Can you explain about defect life cycle?

Answer Posted / anupama

Statuses associated with a bug:
New:
When a bug is found/revealed for the first time, the
software tester communicates it to his/her team leader
(Test Leader) in order to confirm if that is a valid bug.
After getting confirmation from the Test Lead, the software
tester logs the bug and the status of ‘New’ is assigned to
the bug.

Assigned:
After the bug is reported as ‘New’, it comes to the
Development Team. The development team verifies if the bug
is valid. If the bug is valid, development leader assigns
it to a developer to fix it and a status of ‘Assigned’ is
assigned to it.

Open:
Once the developer starts working on the bug, he/she
changes the status of the bug to ‘Open’ to indicate that
he/she is working on it to find a solution.

Fixed:
Once the developer makes necessary changes in the code and
verifies the code, he/she marks the bug as ‘Fixed’ and
passes it over to the Development Lead in order to pass it
to the Testing team.

Pending Retest:
After the bug is fixed, it is passed back to the testing
team to get retested and the status of ‘Pending Retest’ is
assigned to it.

Retest:
The testing team leader changes the status of the bug,
which is previously marked with ‘Pending Retest’
to ‘Retest’ and assigns it to a tester for retesting.

Closed:
After the bug is assigned a status of ‘Retest’, it is again
tested. If the problem is solved, the tester closes it and
marks it with ‘Closed’ status.

Reopen:
If after retesting the software for the bug opened, if the
system behaves in the same way or same bug arises once
again, then the tester reopens the bug and again sends it
back to the developer marking its status as ‘Reopen’.

Pending Rejected:
If the developers think that a particular behavior of the
system, which the tester reports as a bug has to be same
and the bug is invalid, in that case, the bug is rejected
and marked as ‘Pending Reject’.

Rejected:
If the Testing Leader finds that the system is working
according to the specifications or the bug is invalid as
per the explanation from the development, he/she rejects
the bug and marks its status as ‘Rejected’.

Postponed:
Sometimes, testing of a particular bug has to be postponed
for an indefinite period. This situation may occur because
of many reasons, such as unavailability of Test data,
unavailability of particular functionality etc. That time,
the bug is marked with ‘Postponed’ status.

Deferred:
In some cases a particular bug stands no importance and is
needed to be/can be avoided, that time it is marked
with ‘Deferred’ status

Is This Answer Correct ?    5 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What criteria would you use to select Web transactions for load testing?

1634


Why is it impossible to test a program thoroughly or in other terms 100% bug-free?

965


List the type of testing perform to test microsoft excel 2003 give atleast 1 example of each type

1426


write a testing stratgy \ approach for a product that you are use every day (e.g gmail, out look etc)

1446


What is the difference between load testing and performace testing?

678






what is the function generator?

1691


how deployment phase of SDLC differs in product based and in service based company ?

2531


What is defect removable efficiency?

683


What is boundary value testing? Give an example.

702


Pls u can u r mail id to my personal mail id also if they dont want to give u r mail id n comman place

1524


write testcases for open dialogbox

1526


what is the common in all s.o.p (standaed operating procedure)?

1494


How does quality control differ from quality assurance?

620


Can you explain v model in manual testing?

680


what is the difference between test case and result matrix

1675