A Test Run is a one-time execution of a set of test cases within a project. It enables testers to verify the functionality and quality of a system by following predefined test cases and logging the results.

  • Manage testing activities effectively and monitor progress.
  • Verify that all planned test cases are executed.
  • Systematically document results for reporting and analysis.
Test Run

Key Features of a Test Run

1. Purpose

Test Runs are used to execute test cases and record test results such as 

  • Pass
  • Fail
  • Block.

2. Creation

Test Runs can be created in two ways:

  • From a Pre-Created Test Plan: Quickly generate a Test Run using a prepared template of test cases.
  • Manual Test Run: Select and add test cases individually to create a custom Test Run.
Create a Test Run based on a Test Plan
Create a Test Run via Test Runs page

3. Execution

Once a Test Run is started, you can:

  • Execute each test case in the list.
  • Record outcomes and provide additional details like comments, attachments, and defects if necessary.

Learn about running tests here.

4. Reporting

  • Upon completing a Test Run, the system generates an automated Test Run Report that includes:
    • A summary of results (e.g., passed, failed, blocked cases).
    • Detailed logs for each test case.
  • Reports can be exported in CSV, PDF, and viewed online.

Learn about Reports here.

Example of Reports

5. One-Time Execution

A Test Run is executed once. If retesting is required, a new Test Run should be created.

What's Next?

For further assistance, check related guides or contact support—we’re happy to help!