Different Status of Issues in software Testing

Are you confused on different status used for issues/Bugs in Software testing and wanted to gain knowledge on that. Here is the List of different Status used for software testing for every project.

New: When a defect is posted for the first time. Its state is given as new

Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to developer team. It can be directly assigned to developer or development Lead

Open: Its state when the developer starts analysing and working on the defect to fix

Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as “Fixed”

Retest: At this stage the tester does the retesting of the changed code and with fix of issues raised earlier on the same functionality. which developer has given to him to check whether the defect got fixed or not.

Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to reopened. The bug goes through the life cycle once again

Deferred: The Bug changed to deferred state means the bug is expected to be fixed in next release. The reason for changing the bug to this state have many factors.

Rejected: If the developers feel that the bug is not genuine developer rejects the bug. Then the state of the bug is change to rejected.

Duplicate: If the Bug is repeated twice or the two bugs mention the same concept of the bug then the recent/latest bug status is changed to duplicate

Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug is no longer exists in the software tester changes the status of the bug to closed. This state means that the bug is fixed, tested and approved.

Enhancement: The state given as not a bug or enhancement, if there is no change in the functionality of the application.

Leave a Reply

Your email address will not be published. Required fields are marked *

You May Also Like