Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / sridevi
1. New: When the bug is posted for the first time, its
state will be “NEW”. This means that the bug is not yet
approved.
2. Open: After a tester has posted a bug, the lead of the
tester approves that the bug is genuine and he changes the
state as “OPEN”.
3. Assign: Once the lead changes the state as “OPEN”, he
assigns the bug to corresponding developer or developer
team. The state of the bug now is changed to “ASSIGN”.
4. Test: Once the developer fixes the bug, he has to assign
the bug to the testing team for next round of testing.
Before he releases the software with bug fixed, he changes
the state of bug to “TEST”. It specifies that the bug has
been fixed and is released to testing team.
5. Deferred: The bug, changed to deferred state means the
bug is expected to be fixed in next releases. The reasons
for changing the bug to this state have many factors. Some
of them are priority of the bug may be low, lack of time
for the release or the bug may not have major effect on the
software.
6. Rejected: If the developer feels that the bug is not
genuine, he rejects the bug. Then the state of the bug is
changed to “REJECTED”.
7. Duplicate: If the bug is repeated twice or the two bugs
mention the same concept of the bug, then one bug status is
changed to “DUPLICATE”.
8. Verified: Once the bug is fixed and the status is
changed to “TEST”, the tester tests the bug. If the bug is
not present in the software, he approves that the bug is
fixed and changes the status to “VERIFIED”.
9. Reopened: If the bug still exists even after the bug is
fixed by the developer, the tester changes the status
to “REOPENED”. The bug traverses the life cycle once again.
10. Closed: Once the bug is fixed, it is tested by the
tester. If the tester feels that the bug no longer exists
in the software, he changes the status of the bug
to “CLOSED”. This state means that the bug is fixed, tested
and approved.
| Is This Answer Correct ? | 2 Yes | 0 No |
Post New Answer View All Answers
what are the risks and contingencies u had in ur project?
Explain the procedure & path of s/w in testing?
can anyone tell me the questions that can be posed in an interview for a 5 year experienced person in manual testing
How do you test for the coockies for a web application?
What is junit & api?
tell wat u did in ur banking project?
What is test closure?
What is the difference between system testing and integration testing?
how to test the case with 5 combination and inputs
There is only requirements document. You have 10 days and 8 resources to release the system.At the end of the 8th day u tell ur TL that system is ready for release. How will you proceed with the testing process or in other words what all approach you will follow once you get requirements
Why is it impossible to test a program thoroughly or in other terms 100% bug-free?
What is a test server?
How to find that tools work well with your existing system?
Could anyone share FAQs for Test Manager position...
negative test cases on banking domain ?
