How to Create Good Performance Defect Reports?
by Nataliia Vasylyna | August 8, 2014 10:00 am
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[1];
- 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.
Learn more from QATestLab
Related Posts:
- defect: https://blog.qatestlab.com/2011/10/11/main-types-of-defects-in-software-testing/
- How to make a top fitness app with QA: https://blog.qatestlab.com/2021/12/08/fitness-app-testing/
- How to verify the performance of mobile games?: https://blog.qatestlab.com/2018/04/26/mobile-game-performance/
- Peculiarities of Mobile Performance Testing: https://blog.qatestlab.com/2016/08/11/mobile-performance-testing/
Source URL: https://blog.qatestlab.com/2014/08/08/how-to-create-good-performance-defect-reports/