Explain bug life cycle
- 3 Answers
- 7066 Views
- CTS, DELL, TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
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.
| Is This Answer Correct ? | 13 Yes | 4 No |
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".
| Is This Answer Correct ? | 1 Yes | 0 No |
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
| Is This Answer Correct ? | 3 Yes | 3 No |
what r the 2 subdivisions of quality process and where does tesing fit?
What the meaning of code walk through is?
What is fault masking explain with example?
What is closed box testing?
viewing entire results after the batch run in qtp Is there is a easier way view the complete results with out opening one by one test scripts
what is opaque testing?,what is transparent testing
What is the difference between Code Release and Code Build?
What is a software version?
How many test cases will be there for testing the numbers of range -10.0 to 10.0? How it is classifying?
Explain interface?
Explain what is testing type and what are the commonly used testing type?
What is the function of the software testing tool 'phantom'?
Automation Testing 
