Test Report

What is meant by test report?

It is the documented artifact, which comprises, summary of activities carried out during the testing phase, along with the tests execution results, in an organized and readable format. It is a documented object, which is prepared after the completion of the testing phase, used to represent the whole testing process, along with its outcome(s) on paper, for the client as well as for the future purpose. Usually, it involves the usage of metrics, which helps the client or stakeholders, in determining the risks or issues, associated with the software product, along with the suggestions or recommendations.

What is the need of test report?

Test report works as a communication medium between the test team/ test manager and other teams, including client or stakeholders, also. It enables the other teams such as development team, designing team, etc., along with the stakeholders, to go through the whole executed testing process, even without, being the part of the testing phase.

Moreover, the human mind cannot memorize each and everything, for a longer duration. Test report works as a tool which is used to capture and store the complete testing process, from starting to end, for a long period of time, which can be accessed, any time, for the present or future purpose.

Further, it is useful, in monitoring and analysing the progress of the testing phase, such as test coverage, types of testing performed or needs to be performed, defects found or resolved, etc.

Most importantly, it makes the development team or stakeholders, to think over the quality of the software product, and accordingly, may go for its market release.

Components of test report

Generally, following given modules, completes the template of a basic test report.

Product or Project Overview

This includes the brief detailing of the developed software product, to have the little understanding and knowledge about the development project such as Product ID, description, etc.


Each and every process, involves one or more than one objective, to carry out the process, with the pre-defined purpose, in a particular direction. Similarly, test objectives, defines the chief motive or scope, behind the testing activities, such as fulfilment of functional or business requirements, exploring defects in one module or whole software application, test coverage, etc. Further, it may also consist of approaches and testing types, which will be well-suited for the test execution.

Test Summary

It is one of the most important components of the test report, which describes the actual execution of the testing activities that were carried out. This documented object is responsible for covering the following aspects of the testing phase.

  • Number of test cases planned.
  • Number of test cases, actually executed.
  • Number or percentage of test cases passed.
  • Number or percentage of test cases failed.

Logged Bugs/ Defects

This involves the quantity of bugs or defects, found in the developed software project, during its testing. Further, it also defines the severity associated with the each found defects and status of bugs or defects, whether open, closed or resolved. Client and development team, generally concentrates on this module of the test report, as it decides the quality of the software product, which determines the path of the software product, either towards its market release or back to development lifecycle, for improvement.

Apart from the above stated aspects, test reports may also consist of following points

  • Exit Criteria
  • Conclusion
  • Used resources.
  • Definitions and abbreviations of the terms, used during the testing.