Test Run properties describe a particular execution of a Test Case. Check them when investigating a result or comparing runs performed in different environments or testing rounds.
Open the run
Open the Test Case or its linked testing context.
Use the Test Runs list to select the run you want to inspect.
Check the run key and Test Case version so you are viewing the correct execution.
Review the run header, execution properties, and available detail information.
The screenshot shows an older layout. Some lists also display a result tooltip with a run summary; open the run when you need its full context and evidence.
Understand the properties
Property | What to check |
Environment | The environment selected for that execution, such as UAT. |
Version | The Jira release version for the run. This is separate from the Test Case version. |
Sprint | The sprint associated with the execution. |
Tested By | The tester recorded for that run; this is different from the case’s assignee. |
Tested Date | The displayed execution date/time. Check the display time zone when comparing timestamps. |
Tested context | The Jira work item, Test Folder, or Test Plan requirement and iteration used for the run. |
Result | The selected run’s execution outcome. It may differ from the latest outcome in another context. |
Environment, release, and sprint values depend on configuration and the values supplied for execution. They are not automatically filled in every run. A missing optional value does not mean no testing occurred.
Compare runs accurately
Compare the same Test Case version and intended testing context.
Check the environment, release, sprint, and plan iteration before comparing outcomes.
Use the particular run’s date and result rather than assuming a case-list result represents every execution.
Open Actual Result and attached evidence to understand what happened.
Case properties such as Type, Priority, Labels, and maintenance Status describe the Test Case. They are different from execution properties.
If a property looks wrong
First confirm that you opened the intended run. If a correction is required, use the available run property controls with the appropriate permissions, then verify the saved run and affected reports.
For changing several runs, see Bulk Update Test Run Properties and Results. For execution setup, see Executing Test Cases: Overview.