Answers:
Answer #1New: when tester reports a defect
Open: when developer accepts that it is a bug or if the developer rejects the defect, then the status is turned into "Rejected"
Fixed: when developer make changes to the code to rectify the bug...
Closed/Reopen: when tester tests it again. If the expected result shown up, it is turned into "Closed" and if the problem persists again, it's "Reopen".
Open: when developer accepts that it is a bug or if the developer rejects the defect, then the status is turned into "Rejected"
Fixed: when developer make changes to the code to rectify the bug...
Closed/Reopen: when tester tests it again. If the expected result shown up, it is turned into "Closed" and if the problem persists again, it's "Reopen".
Answer #21. New: A bug is opened
2. Open: The bug is reviewed by the test or project manager and then it is assigned to the technology.
3. Pending analysis: Thebug is yet to be looked into.
4. Pending fix: Being looked into but the fix is yet to come.
5a. Not a defect 5b. Retest
6. Retest passed
7. Retest failed
8. Closed
9. Deferred
10. Reopen
2. Open: The bug is reviewed by the test or project manager and then it is assigned to the technology.
3. Pending analysis: Thebug is yet to be looked into.
4. Pending fix: Being looked into but the fix is yet to come.
5a. Not a defect 5b. Retest
6. Retest passed
7. Retest failed
8. Closed
9. Deferred
10. Reopen
Answer #3if defect is valid the flow will be:
New-> Open->Assigned->investigation->Being resolved-> Ready for Retest->Retest passed->close
if defect got retest failed then it is moved to retest failed
New-> Open->Assigned->investigation->Being resolved-> Ready for Retest->Retest passed->close
if defect got retest failed then it is moved to retest failed
| Previous Question | Next Question |
| What does black-box testing mean at the unit, integration, and system levels? | Smoke test? Do you use any automation tool for smoke testing? |