What Information a Good Bug Report Contains

by Nataliia Vasylyna | April 2, 2015 10:00 am

The results of any mobile application testing, desktop testing or web site testing are informative and clear error reports.

Sometimes the developers can decline a defect[1] claiming that they cannot reproduce it, or that it is a software feature, not a bug.

Many declined error reports show incompetency of the test engineer. In order to avoid them one should pay considerable attention to preparation of the test environment, software requirements and error reporting. Professionally written error reports are never declined by the developers.

Novice testers should learn from the very beginning and always keep in mind that attention to details is one the most important qualities for efficient performing functional testing, user interface testing, security testing and so on.

It is known that testers must find and document software bugs, but they also are to provide the required information about them.

An Error Report Should Include:

• clear description of the defect;
• detailed steps to reproduce the defect;
• indication of the important characteristics of the defect such as severity, priority, type and so on;
• illustrations or videos of the defect in the addition.

But a professional tester will also write about the defect cause and suggest several ways of fixing the problem. Such reports considerably simplify work of the developers and increase efficiency of the software testing and the whole project. Besides, developers usually do not decline them.

Related Posts:

• How to Write a Quality Bug Report[2]
• How to Create a Good Bug Report?[3]
• How to Write Good Tets Report?[4]

Source URL: https://blog.qatestlab.com/2015/04/02/what-information-should-a-good-error-report-contain/

---