Additional Info Needed for Bug Report

by Nataliia Vasylyna | March 19, 2014 10:00 am

Bug reports play significant role in software development life cycle. It is impossible and useless to execute web, desktop or mobile application testing without them, as no results of testers’ efforts would be produced.

Software engineers cannot write good code and correct mistakes if they work is not checked and no software bugs are reported.

So, a software tester must write distinct and informative error reports. Good error reports greatly facilitate determining and fixing of the reported software bugs. This way testers make contribution to increasing profitability of the project.

An informative and clear bug reports should contain supplementary information besides common items. A software testing company usually wants its testers to add to each error report attachments, demonstrating the problem.

Usually Supplementary Information for Bug Reports May Be in Form Of:

• screenshots demonstrating the problem;
• video files, showing how the error occurs;
• stack traces.

Stack traces are error messages hidden from user interface. They give useful information about the error and are very helpful for developers, but some technical knowledge is required for getting them.

That is why gathering stack traces may be a problem for novice testers. But if they want to become professionals in web, desktop or mobile testing they should learn how to do it.

Related Posts:

• What Information a Good Bug Report Contains[1]
• 5 Characteristics of a Good Bug Report[2]
• What Title Should Bug Report Have?[3]

Source URL: https://blog.qatestlab.com/2014/03/19/what-additional-information-is-needed-for-bug-reports/

---