get_test_run_results
Paginate execution results for a Jira test run or cycle, with an option to return only the latest execution per item. Use startAt and maxResults to page through values.
Instructions
Page through the execution results of a test run / test cycle (GET /testrun/{key}/testresults/page). An item can have several executions; onlyLastExecutions=true keeps only the most recent one per item, so it never returns more values than the run has items. Creating a run already seeds one 'Not Executed' execution per item (that execution IS the item's last one), so with onlyLastExecutions=false — the default — total starts at the item count, not at 0. Older Zephyr Scale builds have no /page endpoint: the deprecated flat GET /testrun/{key}/testresults is then read and paginated client-side, and onlyLastExecutions is resolved from the run object, whose items[] name the id of each item's last execution; the note in the response says which path produced the values (a run that does not exist still surfaces as a 404). Values come in the order the API returns them, which is neither run-item order nor execution order. Returns { startAt, maxResults, total, count, isLast, values, note? } where total is the size of the set being paged — the number of results on the server, or the post-deduplication count when onlyLastExecutions is true — and isLast is startAt + count >= total.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| startAt | No | 0-based index of the first result to return (default 0) | |
| maxResults | No | Maximum number of results to return (default 50; the API server-side default is 200) | |
| testRunKey | Yes | Test run (cycle) key, e.g. PROJ-R123 (PROJ-C123 on older instances) | |
| onlyLastExecutions | No | true returns only the last execution of each run item; omitted means the API default (false — all executions) |