Defects Management

When logging a defect, which information should be included?

• Defect_ID
• Defect Description/title - Detailed description of the defect including information about the module in which defect was found.
• Version - Version of the application in which defect was found.
• Reproduce Steps - Detailed steps along with screenshots with which the developer can reproduce the defects.
Expected Result, Actual Result
• Date Raised - Date when the defect is raised
• Reference- where in you Provide reference to the documents like . requirements, design, architecture or maybe even screenshots of the error to help understand the defect
• Detected By
• Status - Status of the defect
• Fixed by - Name/ID of the developer who fixed it
• Date Closed - Date when the defect is closed
• Severity
• Priority

• Severity VS Priority

Severity describes the impact of the defect on the application/system,  for example, the system is still working or broke down.
Critical: Nothing can proceed further
Major: Certain parts of the system remain functional
Medium: The system is still functional
Low: It won't cause any major break-down of the system

Priority is defined as the order in which a defect should be fixed. Higher the priority the sooner the defect should be resolved.
Low: The Defect is an irritant but repair can be done once the more serious Defect has been fixed
Medium: During the normal course of the development activities defect should be resolved. It can wait until a new version is created
High: The defect must be resolved as soon as possible as it affects the system severely and cannot be used until it is fixed

Some defects may be low severity, but high priority. For example, wrong company log doesn't affect the major function, but it definitely need be corrected before releasing.

Some defects may be high severity, but low priority. For example, typing random symbols in number text box may cause system crash, but it is a rare case. Then it's a low priority defect.

QA can't decide the severity and priority. Normally product manger will be responsible for that.

• Defect Status

New, Assigned
Open, Fixed, Failed, Confirmed/Verified, Closed, Reopened
Duplicate, Not a Defect
Deferred, Rejected


QA->QA Lead (approved)->Dev Lead, PM(reviewed)->Dev (Assigned, Fixed, Rejected)->QA(retest,pass,failed)->Dev