Stages in defect life cycle are below.Pelase note that the below stages may vary from one defect management tool to another. For example Jira might use some of the below stages for defect life cylce and bugzilla but use some of the same and maybe not all of the below.
- New-tester raises a defect and put its status to new.
- Open-test manager goes through the defect and if he thinks the defect is valid he changes the status to open and assigns the status to developer.In some cases tester can himself raise the bug and change status to open and then assigns it to the developer.
- Assign-Developer changes the status to assign. Developer works on it and fixes it.
- Fixed-Developer changes the status to fix.
- Reject-Developers can even reject the defect saying it is not valid at all.
- Defer-developers can even defer a bug to future stage without fixing it if it is going to affect other stages. If tester still feels it is valid he can reopen it.
- Verification-Then last stage is verififcation.tester verifies whether the defect is fixed or its still there by re-testing the application.
- Reopen-After verification is done if tester feels bug is still there tester can reopen the test and send to developer again.
- Close-finally the tester changes the status to close.
Generally testers can open defect, verify it, reopen it and close it.
Developers can fix or reject the defect or defer it but can’t close it.only testers can close it.