A Model for Defect Life Cycle
application based on the Test Procedures. The activities may include FunctionalTesting, Non-Functional Testing, Performance Testing, etc.
Defects may be found
During testing testers may find defects either in the application or in the documentse.g. test procedure.If a defect is found, either in the application (source code) or in the document, adefect report form is filled and passed on to the test team lead or test manager for review. (There is a detailed explanation on what to include in the defect form in thisarticle: Defect Reporting).
Defect Status: Open and Not Reviewed
Stage 2: Defects are reviewed and delegated
Defects get reviewed first by test team lead for any obvious mistakes by the testers,such as missing information on the defect form (see Defect Reporting) and thenreported to software development manager for further review.A meeting is scheduled which includes members of the development team andtesting team to discuss the validity, severity and priority of the defects.At this stage, defects are categorized into three different states:Not a defectDefect will be fixedDefect won’t be fixed in this release
Defect Status: Reviewed & Assigned
Stage 3: Defects are debugged and removed
After the meeting and agreed actions, the software development manager delegatesdefects to different developers in the team.For defects that are not going to be fixed in the current version of the software, animpact analysis must be performed to identify any potential failures that may occur asa result of the existing defects in the system.Developers will analyse the source code to identify the root cause and ultimatelyremove the defect.
Defect Status: Being Debugged
Stage 4: Removed defects are confirmed
www.testingexcellence.comPage 3 of 4