The document describes the defect/bug life cycle and its various states from new to closed. It also outlines the components of a defect reporting template including the defect ID, summary, description, steps to reproduce, expected behavior, priority, severity, assigned developer, status, and environment. An example of a defect report is also provided.

1. Defect/Bug Life Cycle

3. Defect Life Cycle States:
∙ New - Potential defect that is raised and
yet to be validated.
∙Assigned -Assigned against a
development team to address it but not yet
resolved.
∙Active - The Defect is being addressed by
the developer and investigation is under
progress.At thiere are two possible
outcomes; viz - Deferred or Rejected.

4. Test - The Defect is fixed and ready for
testing.
∙ Verified - The Defect that is retested and
the test has been verified by QA.
∙ Closed - The final state of the defect that
can be closed after the QAretesting or can
be closed if the defect is duplicate or
considered as NOT a defect.
∙ Reopened - When the defect is NOT
fixed, QAreopens/reactivates the defect.

5. ∙ Deferred - When a defect
cannot be addressed in that
particular cycle it is deferred
to future release.
∙ Rejected - A defect can be
rejected for any of the 3
reasons; viz - duplicate
defect, NOT a Defect, Non
Reproducible.

6. •Defect ReportingTemplate
∙ DefectId :Aunique identifier of the defect.
∙ Summary :Aone-line summary of the defect,more like a defect
title.
∙ Description :Adetailed descriptionof the defect.
∙ BuildVersion :Version∙ Actual Behavior–The of the buildor
releasein which defect is found.
∙ Steps to reproduce :The steps to reproduce the defect.
∙ Expected Behavior:The expectedbehavior from which the
applicationis deviatingbecause of the defect.
current erroneous state of the application w.r.t. the defect.
∙Priority :Based on the urgency of the defect,this field can be set on
a scale of P0 to P3.
∙ Severity:Based on the criticalityof the defect,this field can be set
to minor, medium, major or show stopper.

7. Reported By :Name of the QA, reporting the defect.
∙ Reported On :The date on which the defect was raised.
∙ Assigned To :The person to whom the defect is assigned
in its current state. It can be the developer fixing the
defect, the QAfor verification of the fixed defect or the
manager approving the defect.
∙ Current Status :The current status of the defect (one of
the states of the defect life cycle).
∙ Environment :The environment in which the defect is
found – release, staging, production, etc.

8. Example:
Bug Name: Applicationcrashes upon clicking the SAVE button
while creatinga new user. Bug ID: (It will be automatically created
by the BUG Trackingtool once you save this bug). Area Path:
USERS menu -> New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
SoftwareTesting 5 Page 9
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date

9. Reason:Defect
Status:New/Open/Active(DependsontheToolyouareusing)
Environment:Windows2003/SQLServer2005
Description:ApplicationcrashesuponclickingtheSAVEbuttonwhilecreatinga
newtheuser, henceunabletocreateanewuserintheapplication.
StepstoReproduce:
1)LoginintotheApplication.
2)NavigatetotheUsersMenu->NewUser
3)Filledoutalltheuserinformationfields.
4)Clickedonthe‘Save’button.
5)Seenanerrorpage“ORA1090Exception:InsertvaluesError…”
6)Seetheattachedlogsformoreinformation(Attachmorelogsrelatedtothe
bug..IFany)
7)Alsoseetheattachedscreenshotoftheerrorpage.
ExpectedResult:OnclickingtheSAVEbutton,youshouldbepromptedtoa
successful message“NewUserhasbeencreatedsuccessfully”.
(Attach‘applicationcrash’screenshot.IFany)
SavetheDefect/BugintheBUGTRACKINGTOOL.YouwillgetaBugIDthat
youcanuse forfurtherbugreference.

10. THANK YOU