It allows developers to replicate the bug easily. See the difference between Error, Bug, Defect and Failure here. If you liked this video, then please subscribe to our YouTube Channel for more video tutorials. The Defect ID will be generated automatically in case of defect management tool. It should contain specific terms related to the actual issue. Be specific while writing the title. Assume, you have found a bug in the registration page while uploading a profile picture that too a particular file format i.
System is crashing while uploading a JPEG file. Who Detected: Specify the designation of the one who found the defect. How Detected: In this field, you must specify on how you have detected such as while doing Testing or while doing Review or while giving Walkthrough etc. Project Name: Sometimes, we may work on multiple projects simultaneously. So, choose the project name correctly. Mention the build version details clearly.
If its just a request for a new feature then you must specify it as Enhancement. Environment: You must mention the details of Operation Systems, Browser Details and any other related to the test environment in which you have encountered the bug. Priority: Priority defines how soon the bug should be fixed. Usually, the priority of the bug is set by the Managers. Actual Result The actual result you received when you followed the steps.
Expected Results The expected results. Attachments Attach any additional information like screenshots and logs. Remarks Any additional comments on the defect. Defect Probability Probability of the Defect. Status The status of the defect. In other words, do not be lazy. Developers may or may not use all the information you provide but they sure do not want to beg you for any information you have missed. Reproduce the defect: Do not be impatient and file a defect report as soon as you uncover a defect.
Replicate it at least once more to be sure. If you cannot replicate it again, try recalling the exact test condition and keep trying.
However, if you cannot replicate it again after many trials, finally submit the report for further investigation, stating that you are unable to reproduce the defect anymore and providing any evidence of the defect if you had gathered. Review it at least once.
Remove any typos. So using the Pivot table, try to summarize your defects by Status or Priority or Severity as per project demands. You can include colorful Pi Charts , Check the sample below:.
If your manager asks or your client demands, you will have to share the Test Execution Report as well. But this is optional when you are sending Defects Status.
Just for additional info to provide, you can include Test Execution Summary snapshot as below:. You can export defects in excel file from these tools, format it well, and can attach that report in the mail.
Below columns should be included in the Defect Status Report from the tool. Please find the attached Sample Defect Status Report in excel.
You can just update the Detailed defect report with your actual defects and refresh Summary tables on the Summary sheet to get your data.
0コメント