Page History
A Test Run (sometimes simply referred as a "run") results from the scheduling of a Test for execution within some Test Execution. Therefore, each time you run some Test, you're in fact running a Test Run.
A Test Run is an internal instance of a Test scenario with different working conditions, such as a different environment or source code, that is used to validate some specific version of source code/SUT, in a specific environment. Various test runs allow to easily detect defects in the code that could lead to system failures. A Test Run is therefore each association between a different Test and Test Execution issues.
A Test Run is not a JIRA issue itself; it's an Xray internal entity that you can search (see see Enhanced querying with JQL).
Normally, you may see Test Runs within specific panels, namelly in a Test Execution (a test run per each test) or within the Test issue screen (history of previous runs for that test).
| Info |
|---|
A Test Execution represents a task for running several Tests. It contains as much Test Runs as the amount of Tests associated to it; to be precise one Test Run per associated Test, in order to track the result for each Test. |
| Table of Contents |
|---|
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.
As an example, general custom fields, summary, description fields are not persisted 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 persisted within the Test Run.
| Manual Tests | Cucumber Tests | Generic Tests | |
|---|---|---|---|
| Test |
|
|
|
| linked Pre-Condition(s) |
|
|
|
Since a Test Run is related with the execution of a Test, obviously it also contains comments and information about linked defects and evidences (i.e. attachments).
Execution History
The execution history of a given Test issue is available in the Test issue view page screen in the section named "Test Runs".
The Test Runs section is headlined by the Test Runs Filter, that allows the user to sort for:
...
- the Project
...
- which 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 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;
Actions
The following actions are available in the Test issue screen.
The "Execute Test" and "Execute Test Inline" may also be available in similar Test Runs sections that may be present in other places.
| Table of Contents | ||||
|---|---|---|---|---|
|
...
To view the execution details:
Step 1: Open the test Test issue you wish to view the test execution details.
...