It is basically an error in coding which causes unexpected results from a Software Program which does not meet actual requirements.<\/p>\n
A Software Test Engineer might come across such defects while executing the Test Cases.<\/p>\n
<\/p>\n
What is a Defect Document\/Bug Report<\/h3>\n
It is a detailed document about the Defects found in the Software Application.<\/p>\n
A Defect Document contains each detail about the bugs like Issue, Description, Date when the defect was found, QA who raised it, Developer who will fix it etc.<\/p>\n
We should include the below information while creating a Defect Document\/Bug Report \u2013<\/p>\n
- \n
- Defect_id:<\/strong> It is a unique identification number for the Defect.<\/li>\n
- Description:<\/strong> Detailed description of the Defect<\/li>\n
- Expected Result:<\/strong> It talks about the expected behaviour of the Application.<\/li>\n
- Actual Result: <\/strong>It talks about the Actual behaviour of the Application.<\/li>\n
- Steps to Reproduce the Defect:<\/strong> How a Developer can reproduce the Defect in the local environment.<\/li>\n
- Date raised:<\/strong> Date when the defect was raised.<\/li>\n
- Reference:<\/strong> It includes the screenshots of the error, Business Requirement etc.<\/li>\n
- Detected By:<\/strong> Name\/User ID of the QA who raised the Defect.Status: Status of the Defect<\/li>\n
- Fixed By:<\/strong> Name\/User ID of the Developer who will fix the Defect.<\/li>\n
- Date Closed:<\/strong> Date when the Defect is closed.<\/li>\n
- Severity:<\/strong> It talks about the impact of the Defect on the Application. <\/li>\n
- Priority:<\/strong> It talks the urgency to fix the Defect.<\/li>\n<\/ul>\n
A Sample Bug Report Template<\/h5>\n
- Description:<\/strong> Detailed description of the Defect<\/li>\n