Published Date: July 8, 2024
Validated: Yes
Audience: Everyone
Products and Versions Covered:
- Jama Connect®
Summary
Test Plans have no status. Test Case Status is a field determined by the lowest status of the most recent Test Run in any active Test Plan, regardless of when the Test Run was created. Archived Test Plans are excluded from status evaluation.
Resolution
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.
If no Test Runs are associated with the Test Case, its status is NOT SCHEDULED.
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.
The default setting includes existing and new organizations in the calculation, as well as 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 reflects the state of the last edited test run for 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.
Note: Because test case status is calculated automatically, it can't be updated manually when editing a test case.
Tip: If a test case is used in multiple plans and it reflects the status of a plan that is no longer relevant, one option is to archive that plan. Doing so removes the plan's test-run statuses from the test-case status calculation.
You can also use archiving to trigger a recalculation of all test cases for a plan. When a user archives and then unarchives the test plan, it results in a re-calculation of the status for all test cases in that plan. This can be helpful if you change the admin setting to include unexecuted test runs (which isn't retroactive) and want to recalculate test case statuses with the new setting.
Additional Resources
- Success Programs
- Success Catalog
- Datasheets
- Request a Solution Offering or Training from the Success Catalog
Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.
Comments
1 comment
As the test case status is calculated, it is not changed when the status of the test case itsself changes (e.g. due to a change in test case description).
the test plan out of sync symbol does highlight this, but testers are bound to oversee them. A filter or report should be available to show all test runs that are (most likely) invalid as the test case has changed.
How do I get this info? Any API examples and how should I use these?
thanks.
Please sign in to leave a comment.