What is a Test Run?

A Test Run (sometimes simply referred to as a "run") occurs when a Test is scheduled to execute within a Test Execution. Therefore, each time you run a Test, you're, in fact, running a Test Run.

A Test Run is an internal instance of a Test scenario that is used to validate some specific version of source code/SUT, in a specific environment. Various Test Runs allow you to easily detect code defects  that could lead to system failures.

A Test Run is not a Jira issue; it's an Xray internal entity that you can search (see Enhanced querying with JQL).

Normally, you may see Test Runs within specific panels, such as in a Test Execution (a test run per Test) or within the Test issue screen (history of previous runs for that Test).


A Test Execution represents a task for running several Tests. It contains as many Test Runs as the number of Tests associated with it. To be precise, there is one Test Run per associated Test, in order to track the result for each Test.

What is stored in a Test Run?

A Test Run contains a copy of the testing specification of the Test and associated Pre-Conditions. This specification only comprises some fields of these entities; thus, not all fields are copied to the Test Run.

General custom fields, summary, description fields are not replicated in the Test Run. Thus, you should avoid using those fields to add "relevant" information to the test specification. 

Depending on the original type of  the Test associated with this Test Run, these are the fields are replicated in the Test Run.


Manual TestsCucumber TestsGeneric Tests
Test
  • Test Type
  • manual steps
  • Test Type
  • Scenario
  • Test Type
  • Generic Test Definition
linked Pre-Condition(s)
  • Pre-Condition(s) Type
  • Conditions
  • Pre-Condition(s) Type
  • Conditions
  • Pre-Condition(s) Type
  • Conditions


Since a Test Run is related to the execution of a Test, obviously, it contains comments and information about linked defects and evidences (i.e., attachments).

Data consistency

Test Runs represent the results of running some Test specification at some moment in time, in the context of some Test Execution. Thus, they assure data consistency. 

So, what happens if you change the Test specification at any time? Your existing Test Runs will not change (unless you want them to), in order to ensure data consistency and compliance with conformance regulations.

At the execution screen of a given Test Run, you will be presented with two options:

  1. Merge current Test specification with the current specification in the Test Run
  2. Reset the current Test Run, by copying the current Test specification to the Test Run and discard all recorded results


More information on these actions can be found in the Execute Tests page.

Execution History

The execution history of a given Test issue is available in the Test issue screen in the "Test Runs" section.


The execution history of a given Test issue is available in the Test issue screen in the "Test Runs" section.

The Test Runs section is headlined by the Test Runs Filter that allows you to filter for:

  • the Project in which the Test Execution the current Test is associated with
  • the target release Version tested by the Test Execution the current Test is associated with
  • the Status of the Test Execution the current Test is associated with
  • the Start and End dates of the Test Execution the current Test is associated with
  • the Test Environment of the Test Executions the current Test is associated with
  • the Clear button that empties all the Test Runs Filter fields

The search results are displayed on the table immediately under the Test Runs Filter, containing the following columns:

  • the Execution Key of the listed Test Execution the current Test is associated with
  • the Fix Version tested by the listed Test Execution the current Test is associated with
  • the System Revision tested by the listed Test Execution the current Test is associated with
  • the Exec by who is the Assignee of the listed Test Execution the current Test is associated with
  • the Start and End dates of the listed Test Execution the current Test is associated with
  • the Defects related with the listed Test Execution the current Test is associated with
  • the Status of the listed Test Execution the current Test is associated with

View Test Run Details

To view the execution details:

Open the Test issue you wish to view the test execution details.

Click the Execute button that appears in the last column of the desired Test Run that is in a final state. The actions menu should pop up with the available actions.

Click Execution Details action to open the Execution page and view the details.