DEFECT LIFE CYCLE
A defect is in open state when the tester finds any variation in the test results during testing, peer tester reviews the defect report and a defect is opened. Now the project team decides whether to fix the defect in that release or to postpone it for future release. If the defect is to be fixed, a developer is assigned the defect and defect moves to assigned state. If the defect is to be fixed in later releases it is moved to deferred state. Once the defect is assigned to the developer it is fixed by developer and moved to fixed state, after this an e-mail is generated by the defect tracking tool to the tester who reported the defect to verify the fix.
The tester verifies the fix and closes the defect, after this defect moves to closed state. If the defect fix does not solve the issue reported by tester, tester re-opens the defect and defect moves to re-opened state. It is then approved for re-repair and again assigned to developer. If the project team defers the defect it is moved to deferred state, after this project team decides when to fix the defect. It is re-opened in other development cycles and moved to re-opened state. It is then assigned to developer to fix it.
CLASS ACTIVITY
Sit In your groups Select 5 defects of your software that you are testing so far Create the defect cycle and log for each of those Presentations This activity carries 5 points
ASSIGN DEFECTS
Select the person you are assigning defects to, follow your defect log. You have 15 mins to present