How Does the Status of a Test Run Factor Into the Status of a Test Case?

Amanda Jennewein
Amanda Jennewein
  • Updated

Author: Carmen Santos

Updated: July 2024

Audience: Everyone

Products Applicable: Jama Connect®

Use Case

How Does the Status of a Test Run Factor Into the Status of a Test Case?

Best Practice

Test Plans have no status. Test Case Status is a field derived from the lowest status of the last executed Test Run in any active Test Plan (regardless of the order of the Test Run's creation).
Archived Test Plans will not be taken into consideration for status evaluation.


Screenshot 2024-07-08 at 2.54.42 PM.png

To keep irrelevant plans from affecting the Test Case status, you can archive superfluous Test Plans. To do this, right-click Test Plan > Archive. You can unarchive the Test Plans as they still appear in the list and are grouped as Archived Test Plans.

Screenshot 2024-07-08 at 2.55.14 PM.png

If no Test Runs are associated with the Test Case, its status is NOT SCHEDULED.

Screenshot 2024-07-08 at 2.56.00 PM.png

The status of a test case is determined by the most recent test run from all active test plans that contain it. This means a test case can fail even if all test plans' most recent test run is marked as passed.Screenshot 2024-07-08 at 2.57.30 PM.png

The default setting includes existing and new organizations in the calculation and any unexecuted test runs. To include only executed test runs in the computation, uncheck this option. However, please note that this change will not apply to previous calculations.

*If you generate a Test Plan report, the Test Case Status in that report will be based on the most recent run in any plan, not that plan specifically. You will need to archive a test plan if you want the status of its runs to be independent of the Test Case Status.

More on Test Case Status

Test case status is a calculated status that indicates the state of the last edited test run associated with that case.


By default, the status is calculated using all available test runs associated with the test case, including unscheduled runs. An organization administrator can turn off this option so that unexecuted runs aren't included in the calculation.


The status is calculated in one of these methods:

  • If the test case is used in only one test plan, the latest status is reported on the test case.
  • If the test case is used in multiple test plans, it shows the most urgent test run status based on the following hierarchy, regardless of when it ran: Not Scheduled, Failed, Blocked, Scheduled, Passed.

The status is visible in the Single Item View of each test case.



Because test case status is automatically calculated, it can't be manually updated when editing a test case.


If a test case is used in multiple plans and it's picking up the status of a no longer relevant plan, one option is to archive that plan. Doing so removes that plan's test run statuses from the test case status calculation.

You can also use archiving to trigger a plan recalculation of all test cases. When a user archives and then un-archives the test plan, this results in a re-calculation of the status for all test cases in that plan. This can be useful if you change the admin setting to include unexecuted test runs (which isn't retroactive) and want to recalculate test case status with the new setting.

Please feel free to leave feedback in the comments below.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.