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

when developers sends you a build.what the test engineer does?

2 Answers  

---

Write the test cases for godaddy home page

0 Answers   ABC,

---

i m going to pay for air reservation online and i m paying through credit card supose i give credit card no 123456.how u chk this is valid or not.wat validation u put for kind of fields

2 Answers   informatics,

---

How to do cards Testing? And give sample test cases please? And tell me about vision plus card?

0 Answers  

---

How much interaction with users should testers have, and why?

1 Answers  

---

what is verification and Validation?

12 Answers   Oracle,

---

Anyone attended the manual testing interview with L&T infotech in recent past. please let me know the type of questions they can ask especially in PM round. Thanks

0 Answers  

---

How much time it will take for regression testing

6 Answers   AppLabs,

---

Why documentation testing is important?

0 Answers   Virchow,

---

Imagine you are in an empty room with a fan, a bulb and an air conditioning system. There is a switch board on the wall with 32 switches and 2 plug points. You are tasked with testing this setup. Assume you are not given any requirements whatsoever. How would you approach it? What would be your priorities? If you make any assumptions, do state them.

1 Answers  

---

You have been given 2 projects to test, what are the key factors you consider when prioritizing you work load?

1 Answers   Syncada,

---

how is market for testing in banglore,chennai,pune,delhi?

0 Answers   IBM,

---