5 Characteristics of a Good Bug Report

5 Characteristics of a Good Bug Report
April 04 10:00 2014 Print This Article

The only tangible result of any web site, desktop or mobile testing is bug reports. That is why testers should be very serious about error reports and write them thoroughly.

Creating of clear and laconic error reports is not as easy as it may seem. Sometimes it is hard to explain to other people what is obvious for you. So, a software testing company wants its testers to learn how to express their ideas and observations through words.

A Proper Error Report Should:

  1. Be clear and univocal. Title, description and steps to reproduce must be distinct and informative.
  2. Give briefly presented information. Too long and diffusive explanations only take time and confuse the developers.
  3. Contain supplementary materials in form of screenshots or video. Visual representation of a defect always helps to understand the problem better and shows details that can be omitted in the word description. Video of a defect is often necessary to make during mobile testing, when movements are involved.
  4. Comprise suggestions about how to enhance the software product or how to correct the error. This information may be useful for programmers.
  5. Include detailed description of the environment in which the reported defect occurs.

Such error reports are understandable, sufficient and brief. They demonstrate that mobile application testing, desktop testing or web site testing is performed by professionals.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.