What makes a good defect report

In case if your bug report will be good on, it helps your developers to fix it and make the more reliable product. And if you write your bug report effectively then bug have more chances to be fixed. So fixing bugs are directly dependent on how you report it. Anyone can write a bug report. But not everyone can do it effectively.

You should be able to distinguish between a mediocre bug report and a good one. How to distinguish a good or bad bug report? Otherwise, the more likely that the developer will simply proceed to the next bug report. In the description of the bug, you must to clearly describe the steps to reproduce without missing any of them. Specific and Informative — do not spread problem in the whole essay. Try to be specific and maximise informatively. Strive to summarize the problem in minimum words yet in an effective way.

Write different reports for each problem. So the goals of a bug report are to:. Title : In title should be a short explanation of what the issue is.

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. Use of simple word which everyone understand easily. You should be objective while defect reporting. The Severity describes the impact of the bug. It is given by tester while adding the defect. The Priority tells about When bug should be fixed?. It can be setup by manager or lead or defect triage team while reviewing the defect. It is very easy to filter out the defects based on these values. Prepare a simple checklist in your mind, basically they are more like guidelines and always check the defect with the checklist before reporting like spelling check, grammar check, and style check.

Once defect draft is ready, read defect twice to check the clarity of defect. If you missed to do this then it might be possible to report a defect with a simple mistakes which creates a bad impression in front of your team about your defect reporting skill. Few are report a defect with single liner description with efficiently communicate the exact defect with developer.

In upcoming article I will explain about Bug report template with sample bug report. If you are not regular reader of this website then highly recommends you to Sign up for our free email newsletter!

Sign up just providing your email address below:. Dear sir, This is jyothi, am passout, am trying on 2yrs of exp, please help me to do real time projects and real time experiance. Sir forward me some projects for practice. Once you have isolated a specific bug, be sure to check wether the case happens in a very specific setting, or in a broader setting. If you noticed it for an international customer, does it also happen to a national one? And, of course, once the exact perimeter is properly delimited, report accordingly :.

Software Testing Class. STC Admin July 14, Nice article it is very useful. Thanks Reply.