Scribd
Upload
8 views1 page

9.defect Life Cycle

The document outlines the Defect Life Cycle, detailing stages from 'New' when a defect is first identified to 'Closed' when it is verified as fixed. It includes intermediate stages such as 'Assigned', 'Open', 'Fixed', 'Pending Retest', 'Retest', 'Verified', 'Reopen', 'Duplicate', 'Rejected/Not a Bug', and 'Deferred'. Each stage describes the status and actions taken regarding the defect throughout the testing and development process.

Uploaded by

MEERA SUPERSTORE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
8 views1 page

9.defect Life Cycle

The document outlines the Defect Life Cycle, detailing stages from 'New' when a defect is first identified to 'Closed' when it is verified as fixed. It includes intermediate stages such as 'Assigned', 'Open', 'Fixed', 'Pending Retest', 'Retest', 'Verified', 'Reopen', 'Duplicate', 'Rejected/Not a Bug', and 'Deferred'. Each stage describes the status and actions taken regarding the defect throughout the testing and development process.

Uploaded by

MEERA SUPERSTORE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Defect Life Cycle:

----------------------
New:
-------
When the defect is found and posted for the first time.

Assigned:
------------
Once the defect is posted(bug), we will assign to developers.

Open:
--------
Once the developer opens the bug and check whether it is valid or invalid.

Fixed:
--------
When developer fix the bug with appropriate codes.

Pending Retest:
--------------------
Once the develper fix the bug, it will be moved to testing team.

Retest:
---------
When the tester retesting whether the bug raised was fixed or not.

Verfied:
----------
If the tester confirms that the bug is fixed.

Reopen:
-----------
If the tester confirms that the bug is not yet fixed and found the same defect.
Again it will be moved to Assinged Stage and the flow continous.

Closed:
---------
Once the tester verfied that the bug is fixed, then the defect raised will be
closed.

Duplicate:
-------------
If the bug is already raised by someone, and if it is raised again means it is
duplicate.

Rejected/Not a Bug:
--------------------------
When the developer feels that the bug is not genuine.

Deferred:
-------------
The bug which developer feels that it can be fixed later on the upcoming
sprints/releases.

You might also like