• info@helpingtesters.com
  • helpingtesters

Test Execution Report Template

December 23, 2017 Software Testing Templates
test execution reports, test execution report, sample test execution report, test execution report template, test execution report sample template, test summary report

As a tester, you have to create, use and deliver various reports and documents to the development team, testing manager and product owner. These are generally used by the project manager, product owner, and other testers to get a brief overview of the testing progress, and how testing is being conducted for the impending release. One such reports to be shared across the team is Test Execution Reports.

Download Test Execution Report Template

Of all the test reports used daily by users, in this post, our primary focus would be to understand the complete structure and get used to the various components of a test execution reports. We would also share a dummy test execution report template which you can refer to for your own understanding.

What are the different reports generally used in Testing

Before detailing out a test execution reports, let’s find out the basic reports used by testers.

⇒ Daily Status Report

Daily status reports or updates is one of the test execution reports, that contain information about the different tasks performed, tasks executed, issues logged and hurdles faced by a tester.

  • Every member of the testing team creates a daily status report and send it forward to their test manager at the end of each day.
  • The status report consists of updates related to :
    • What different testing or tasks did you performed today?
    • What tasks are the planning tomorrow?
    • Were any blockers encountered while executing today’s tasks?
  • The status report can be in any format of choice depending on the needs of the project manager. Team members can mail their daily statuses directly to their managers or update it in a centralized portal or spreadsheet.
  • For strict Agile teams, Daily SCRUM meeting eradicates the need for a daily status report, as all updates are conveyed during the meeting.
  • The data from the daily status report of each tester is processed by the project manager, and an overview of the testing team’s progress is shared with the client/ product owner.

⇒ Testing Reports

The testing reports talk specifically about the current test deliverables, how testing should be conducted and progress made in testing. Let’s talk about the 3 primary testing reports which are often used by testers.

  • Test Plan status report – As the name suggests, the test plan status report shows the current status of the test plan.
    • This report notifies the team, whether any changes are being made to the existing test plan or any new version is introduced.
  • Test Documentation Status – Test Documentation lets the team know the status of test documents. The test documentation status shows the status of the test cases, and test scenarios while the project is in the design phase.
    • This report notifies the testing team of the progress of the test documentation and when the different documents need to be reviewed.
  • Test Execution Status – The test execution report is the primary focus of this article. The test execution report tells the testing team, the project manager, and the product owner, what the status of testing is, and how stable the overall application is.
    • Depending on the team and the type of project, the test execution report can be sent on a daily basis or on a weekly basis.
    • The test execution report shows the number of test cases passed, failed, blocked or not executed. It also enlists the bugs encountered during the test execution phase. We would talk about the different components of a test execution report in the following sections.
    • As the report contains detailed test execution status, such reports are generally shared over mail and discussed during retrospective or before the demo.

What are the primary components of Test Execution Reports?

Test execution reports are mostly created in spreadsheets. The basic components of test execution report can be broadly classified into 3 categories, namely 

Test Report Summary

The test summary gives a brief overview of the overall execution status.

Figure 1: Test Summary Report

  • In the summary, you can see information related to
    • The number of test cases planned within the cycle.
    • The number of test cases executed within the cycle.
    • The total number of test cases executed till date.
    • Defects encountered within the cycle.
    • Total defects encountered till date.
    • Pass percentage and defect density.
  • The summary section helps the project manager and product owner get a quick overview of the current execution and analyze it to predict any bottleneck that might arise during the testing cycle.

⇒ Test Scenario/ Case status

The next sheet i.e. the test scenario/ test case status gives a detailed report of the status of the test scenarios.

Figure 2: Test Scenario/ Case status

  • It enlists the different scenarios and test cases executed during the testing cycle, along with their corresponding statuses. You can even find the name of the testers who executed the test cases along with a brief description of the issues which were encountered during test execution.

⇒ Reported bugs

Any bugs which were reported during the test cycle are mentioned in this section.

Figure 3: Reported bugs

  • The defect ID, a brief description of the issues, steps to reproduce are mentioned for each and every issue are mentioned here.
  • You can even mention the priority and status of the defect and mention the name of the developer if the issue is already assigned to someone.
  • For ease of use, it is suggested to provide hyperlink and mention the path of the defect as well.

⇒ Hurdles/Impediments faced

It is an optional section and you may or may not add it to your test execution reports.

Figure 4:  Hurdles/ Impediments faced

  • This section is used to bring into focus the pain points and impediments encountered by the testing team during test execution.
  • This section is primarily aimed towards the project manager and product owner. If the problems mentioned in this section are related to infrastructure or resources, the manager can leverage this report to fix the issues to help prevent the same problem in subsequent test cycles.
  • If there were any issues with the test environment, the details and the outcome of this problem should be noted in this section. This will outline the problem and the impact it can have on the application testing.

Now that you are aware of the different components, it’s time for you to try your hands out on a dummy Test Execution reports. You can click this link, to HelpingTesters_Test_Execution_Report.


  • Testers use different testing reports to track the progress of testing. And test execution reports is one of the most important and widely used reports.
  • The test execution reports consist of a brief overview of the items/ modules tested and how stable the application under test is during the testing cycle.
  • It also enlists individual status (pass/ fail or blocked) of the different test cases and scenarios.
  • If any issues are encountered while executing the test cases they are mentioned in the test execution report and shared with the team members and test manager.
  • Test execution reports are handy document which allows the product owner get a quick glimpse of the testing progress and evaluate the stability of the application being developed.

About the author

arindam bandyopadhyay author

Arindam Bandyopadhyay is an automation tester with over 5 years of experience in software testing. While during the day he juggles between Eclipse and spreadsheets, at night he lets his fingers do the talking as he writes about anything and everything his paradoxical mind desires.

Leave a Reply

Your email address will not be published.