Answer / nag

Types of Defects
Generally the Black Box
Testing techniques is finding below type of defects during
system testing such as

? User Interface Defects
? Boundary Related Defects
? Error Handling Defects
? Calculations Defects
? Race Condition Defects
? Load Condition Defects
? Hard Ware Related Defects
? ID ? Control Bugs
? Version Control Bugs
? Source Bugs

Note 1:
Generally the Test Engineer?s are deciding
severity & priority of defect during reporting but the
priority of defect is modifiable by development team

Note 2:
Generally the development people are
postponing / differing low severity & low priority defects.

L-S: Low Severity
M-S: Medium Severity
H-S: High Severity
L-P: Low Priority
H-P: High Priority

1. User Interface Bugs / Defects : (L-S)
E.g.1. Spelling mistake (L-S & H-P) Seriousness is low but
importance is high priority.
2. Improper Right Alignment (L-S & L-P)
2. Boundary Related Bugs: (M-S)
E.g.1. One object is not taking valid type of values as
input (M-S & H-P)
2. One object is taking invalid type also (M-S & L-P)
3. Error Handling Bugs: (M-S)
E.g.1. Does not return error message to prevent wrong
operations on build (M-S & H-P)
2. Returns error message but complex to understand (M-S & L-P)
4. Calculations Bugs: (H-S)
E.g.1. Dependent output is wrong (application show stopper)
(H-S & H-P)
2. Final output is wrong (Module show stopper) (H-S & L-P)
5. Race Condition Bugs: (H-S)
E.g. 1. Dead lock or Hang (Application Show Stopper) (H-S & H-P)
2. Does not run on other customer expected platforms (H-S & L-P)
6. Load Condition Bugs: (H-S)
E.g. 1. Does not allow multiple users (Application Show
Stopper) (H-S & H-P)
2. Does not allow customer expected load (H-S & L-P)
7. Hardware Related Bugs: (H-S)
E.g.1. Does not activate required hardware device
(Application Show Stopper) (H-S & H-P)
2. Does not support all customer expected hardware
technologies (H-S & L-P)
8. ID-Control Bugs: (M-S)
E.g.1. Wrong logo, logo missing, copy right windows mixing,
wrong version no. , development and testing people names
missing.
9. Version Control Bugs: (M-S)
E.g.1. Invalid differences in between old build version and
current build version.
10. Source Bugs: (M-S)
E.g.1. Mistakes in help documents.

Answer / satya_k21

Common Defects:
===============

-Page not found (Error 404)
-Server Not foung


Regards,
Satya.k

wat if fiddler and how it is used in tesing an application. please explain with a real time scenario

0 Answers  

---

What is the test case?

0 Answers  

---

How we Check Perfomance testing In Manual? for web application and it is for only web apps or for Client server app's? Plz any body

1 Answers  

---

Write 2 scenarios for Integration testing? Please let me know its urgent.

0 Answers  

---

WHAt is diff between test plan and test planning?

5 Answers  

---

equivalence class partitioning techniques used in system testing or not

1 Answers   iSoft,

---

I have a doubt in writing a test case... if suppose in a round if they ask to write a test case for any situation such as(Search engine)... in the testcase do we need to fill up the actual result and status Column in the test case??(please answer i am confused)

6 Answers  

---

What is meant by Error Guessing?

9 Answers   IBM,

---

Testing mainly in Verification or Validation ?

4 Answers   Crea,

---

what is walkthrough?

6 Answers   Semantic Space,

---

What is Management Testing?

2 Answers  

---

How do you know your code has met specifications when there are no specifications?

2 Answers  

---