A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.
A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.
If a Defect is some time times only appearing then that Defect is not producible defect, we have to provide proof (snap shots or database dumps) for locating it.
The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.Some companies use Manual Process (Excel workbook), and some companies use Tool based process for Defect Management.
Tools Examples:Bugzilla / Issue-Tracker / PR-Tracker/Jira / Quality Center etc...(anyone)
Defect Life Cycle
Different Flows of the Defect :
Terminology vary from one phase to another in Software Application Life Cycle
Software Application Life Cycle has 3 phases;
An occurrence in which one defect prevents the detection of another.
The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g. lines-of code, number of classes or function points).
A Sample Defect Report Template:
No -> Rarely defect appears
If Yes, attach test procedure:
If No, attach snapshot & strong reasons:
Note: Defect Report Template may vary from one company to another and one project to another
A procedure to derive and/or select test cases targeted at one or more defect categories, with tests being developed from what is known about the specific defect category.
The number of defects found by a test phase, divided by the number found by that test phase and any other me afterwards.
Defect Reporting Process:
Defect Reporting Process vary from one company to another.
If a Defect is appearing every time (in every execution) then that Defect is producible defect, we can provide steps for locating it.
A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.
Status of Defects
New: Tester provides new status while Reporting (for the first time)
Open: Developer / Dev lead /DTT opens the Defect
Rejected: Developer / Dev lead /DTT rejects if the defect is invalid or defect is duplicate.
Fixed: Developer provides fixed status after fixing the defect
Deferred: Developer provides this status due to time etc...
Closed: Tester provides closed status after performing confirmation Testing
Re-open: Tester Re-opens the defect with valid reasons and proofs