A defect is an error or bug found in the application. A programmer while designing and developing the software could make mistake. These mistakes or errors are also termed as faults in the software.
While testing a software application or product, if the actual result deviates from the expected result then it is termed as defect.
A Software defect / bug is a condition in software which does not meet the requirement or end-user expectation.
Defect Management Process:
Defect management process includes the following steps:
Identify 
This step involves detecting a defect. The person noticing the defect is mostly someone in the testing team. In the real world, it can be anyone including individuals in the project team, or even the end-user(customer).
Category 
When a defect is reported, it is assigned to a designated team member to confirm that the defect is actually a defect as opposed to an enhancement, or other appropriate category. Once categorized, the defect moved into the process flow and the next step is to prioritize it.
Priority 
Priority is based on combination of the severity of impact on the usability, relative effort to fix, along with a comparison against other defects. The priority should be determined with representatives of the customer and the project team.
Assign 
Once a defect has been prioritized, it is then assigned to a developer or other technical person to fix.
Resolve 
The developer fixes (resolves) the defect and follows the organization&#8217;s process to deploy the fixed code to the environment where the defect was originally identified.
Verify 
Depending on the environment where the defect was found and the fix was applied, the software testing team or customer verifies that the fix is actually resolved the defect.
Close 
Once a defect has been resolved and verified, the defect is marked as closed.
Defect report or Bug report consists of the following information:
<ul>
<li>Defect_ID – Every bug or defect has its unique identification number</li>
<li>Defect Description – This includes the abstract of the issue.</li>
<li>Product Version – This includes the product version of the application in which the defect is found.</li>
<li>Description – This includes the detailed steps to be followed to re-create the issue with the screenshots attached so that developers can recreate it easily.</li>
<li>Date Raised – Date when the bug is reported</li>
<li>Reported By – This includes who reported the bug like tester Name and ID</li>
<li>Status – This field includes the Status of the defect like New, Assigned, Open, Re-test, Verification, Closed, Failed, Deferred, etc.</li>
<li>Fixed by – This field includes the details of the developer who fixed it like Name and ID</li>
<li>Date Closed – Date when the bug is closed</li>
<li>Severity: Based on the severity (Critical, Major or Minor) it tells us about impact of the defect or bug in the software application</li>
<li>Priority: Based on the Priority set (High/Medium/Low) the order of fixing the defect can be made.</li>
</ul>
See Also: <a title="How to identify Cross Site Scripting (XSS) Vulnerabilities threat" href="https://www.andolasoft.com/blog/2014/07/how-to-identify-cross-site-scripting-xss-vulnerabilities-threat.html" target="_blank" >How to identify Cross Site Scripting (XSS) Vulnerabilities threat</a>
Defect management process or bug tracking is an integral part of our Quality Assurance process. <a title="QA Services" href="https://www.andolasoft.com/quality-assurance-service/" target="_blank" >Avail our QA services</a> not just for projects done by us but also for projects done by you or your vendors.
I hope you enjoyed this topic, if you have any questions or comments please share below!

Defect Management Process in Software QA/QC

Table of Contents

Related Articles

Quick Links

Products

For Career

For Sales