How Can Test Reports Be Represented?
by Nataliia Vasylyna | June 3, 2014 10:00 am
Software testing is an intangible process. The only way to demonstrate results of testers’ work is reporting about the discovered errors.
The reports show other stake holders the progress of mobile application testing, desktop testing or web site testing. Their presentation is important element of each testing process and must be considered in a test plan.
Some experts in software testing claim that it is wise to mention about reports in logistics.
It is Necessary to Discuss and to Agree Upon with Other Project Parties:
- what they want to be in the reports;
- in what form the reports should be represented;
- schedule of the reporting.
A software testing company would confirm that reporting may not be limited by logging in software bugs in a bug tracking system. That is why it is wise to determine in what form to present results of web site testing, desktop testing or mobile testing.
Reports About the Testing Progress Can be Represented As:
- error reports and reports showing percentage of executed tests, number of found errors and so on;
- representing information about progress of manual and automate testing and found defects in form of graphics, diagrams and schemes;
- often debriefs with representatives of all the project parties; this form of reports is mostly utilized during session-based testing;
- oral reports;
- specific documents required by the customers.
Learn more from QATestLab
Related Posts:
- Test Design Specification: https://blog.qatestlab.com/2020/05/15/test-design-specification/
- Testing at a Complex Project: QATestLab Real Case: https://blog.qatestlab.com/2019/09/03/complex-project-testing/
- TOP 10 Best Time Tracking Software of 2019: https://blog.qatestlab.com/2019/08/01/top-time-tracking-software/
Source URL: https://blog.qatestlab.com/2014/06/03/how-can-test-reports-be-represented/