Answer Posted / jhuma
A bug life cycle may be like this...........
1.new:-when the bug is first time found/revealed by the tester,he communicates with his lead to be sure about the validity of the bug.If it is valid,then it is reported and the status becomes "new"
2.Assigned:-After a bug is reported new,it comes to the development team and and the lead verifies the bug and if found valid he assigns it to a particular developer.Now the status becomes assigned.
3.open:;when a developer is assigned a bug,he opens it to work on the bug.He changes the status to "open".
4.fixed:-once the developer makes necessary changes to the code,he changes the status to "fixed".
5.retest:-then it comes to the tester for retesting.now the tester changes the status to "retest".
6.closed:-if the tester is satisfied with the changes or the fixing of the bug after retesting,he closes the bug and changes the status to "close".
reopen:-if after retesting,the tester finds any defects or wrong,he reopens the bug and changes the status to"reopen".
7.rejected:-if the developer finds the bug is invalid,he rejects the bug and changes the status to "rejected".
8.Deferred:-if the developer thinks that the bug can be fixed later because of less importance of the bug,he can defer it and now the status becomes "deferred".
| Is This Answer Correct ? | 3 Yes | 4 No |
Post New Answer View All Answers
what are the typical problems in web testing?
is it possible to do performance testing in stand alone application..how wil u do that ???????
How should validation activities be handled?
Explain the defect life cycle.
What is bug leakage?
Which are the standards for software test plans?
What is manual testing and what is it process?
what is mean by impact analysis ,how we used to select regression TC using this?
What is a testbed in manual testing?
Plz give me manual testing real test case ?
what is acid testing?
Test approach to windows scheduler?
What's the relationship between environment reality and test phases?
i want to for technical interview question paper along with in tesrviwe Phases i need
How does your preferred work style work with the ideal test-manager role that you just described? What is different between the way you work and the role you described?