Answer / santhosh k

Bug status description:
These are various stages of bug life cycle. The status
caption may vary depending on the bug tracking system you
are using.

1) New: When QA files new bug.

2) Deferred: If the bug is not related to current build or
can not be fixed in this release or bug is not important to
fix immediately then the project manager can set the bug
status as deferred.

3) Assigned: ‘Assigned to’ field is set by project lead or
manager and assigns bug to developer.

4) Resolved/Fixed: When developer makes necessary code
changes and verifies the changes then he/she can make bug
status as ‘Fixed’ and the bug is passed to testing team.

5) Could not reproduce: If developer is not able to
reproduce the bug by the steps given in bug report by QA
then developer can mark the bug as ‘CNR’. QA needs action to
check if bug is reproduced and can assign to developer with
detailed reproducing steps.

6) Need more information: If developer is not clear about
the bug reproduce steps provided by QA to reproduce the bug,
then he/she can mark it as “Need more information’. In this
case QA needs to add detailed reproducing steps and assign
bug back to dev for fix.

7) Reopen: If QA is not satisfy with the fix and if bug is
still reproducible even after fix then QA can mark it as
‘Reopen’ so that developer can take appropriate action.

8 ) Closed: If bug is verified by the QA team and if the fix
is ok and problem is solved then QA can mark bug as ‘Closed’.

9) Rejected/Invalid: Some times developer or team lead can
mark the bug as Rejected or invalid if the system is working
according to specifications and bug is just due to some
misinterpretation.

Answer / vidya

Bug Life Cycle :

When the tester founds a bug then the status of the bug is "NEW". If the developers accepts that this is a genuine bug then the developer change the status of the bug as "ACTIVE". Developer will work and fixes the defect and will change the status as "RESOLVED" and will assign to the tester. As a tester we have to Re-test the defect and if everything is working fine then change the status as "CLOSED". or Still it is not working as Expected then change the status as "RE-OPEN".

DEFERRED : As said in the earlier answer, if the bug is not relating to this release or for future then those type of defects status will be "DEFERRED".

Answer / amar

new:when the bug has been found and not approved
open:Approved by the team lead
assigned:Assigned to a developer and fixing in process
Need more info:project need some more information
fixed:bug has solved and it is not validated
closed:validated and fix the bug
deferred:bug for the future it has placed
rejected :not a genuine bug
duplicate:the same bug has been placed by the tester two times
invalid:it is not bug
Reopened:even after fixing the bug repeating

Explain ETVX concept?

2 Answers   TCS,

---

What is closed box testing?

0 Answers  

---

how do you convert use cases into test cases?

0 Answers  

---

What is the difference between IE, Opera & Mozilla Firefox in web Testing and which brower will think that is much better? how would u do performance Testing manually for web site.

5 Answers   Symbions Soft,

---

Explain what test plan is? What is the information that should be covered in test plan?

0 Answers  

---

In a reactive approach to testing when would you expect the bulk of the test design work to be begun?

0 Answers  

---

Explain fault?

0 Answers  

---

What is exhaustive testing?

0 Answers  

---

What is Functional, Non-Functional, and Regression used for (i.e. the purpose of each)?

0 Answers  

---

I have the experience of about 1yrs and 6 months in software testing. Now i must have to shift from this due to unavailablity of projects. But for now I am not able to find any opening in testing with 1+ yrs experience. Plz anybody mail me if anybody finds any openings. Thank you

2 Answers  

---

Explain configuration management?

0 Answers  

---

This question is based on ages easy.

1 Answers   EA Electronic Arts,

---