How to Create Good Performance Defect Reports?

How to Create Good Performance Defect Reports?
August 08 10:00 2014 Print This Article

Those who are involved in web site testing, desktop testing and mobile application testing know that software bugs can reproduce always, once in several times or be unreproducible.

Software engineers easily correct an error that can be always repeated following the steps, because it isn’t hard to determine its cause. It is more difficult to fix an error that repeats once in several tries. And often developers can do nothing about unreproducible software bugs as they cannot determine their essence.

All this refers to mobile performance defects as well. In order to create good error reports, testers must provide sufficient and clear information about the reported software bugs.

When a Tester Finds a Performance Defect During Manual Mobile Testing He or She Should:

  • determine how often it reproduces;
  • write clear steps to reproduce the defect;
  • if the operation is very slow, it is wise to measure how much time it takes and add this information to the report.

Professional testers aim for reproducing every found error. Each software testing company believes that one can reproduce any defect if repeat certain sequence of steps in a certain environment. When a tester claims that an unreproducible error occurred in course of mobile testing, desktop testing or web site testing that means that he or she overlooked something or didn’t try enough times.

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.