Skip to main content
GET
Get batch JUnit XML report

Authorizations

Authorization
string
header
required

API key authentication using Bearer token format. The CLI's ta auth access tokens are also accepted; because they name a user rather than a workspace, a user in several workspaces selects one with the x-testerarmy-team header (workspace id or slug).

Path Parameters

batchId
string<uuid>
required

Batch ID

Query Parameters

allowIncomplete
enum<string>

Export a batch with in-flight runs; unfinished runs render as skipped

Available options:
true,
false

Response

JUnit XML report (served as an attachment)

JUnit XML document. One testsuite per group-run batch (named after the group), one testcase per test. Passing runs have no child element; a FAILED verdict is a <failure>; BLOCKED verdicts, runs that crashed before a verdict, and runs that finished without one are <error> (type BLOCKED, the run error code, or MISSING_VERDICT); cancelled, planner-skipped, and unfinished runs are <skipped>. Each testcase carries testerarmy_* properties plus TestRail testrail_result_comment and testrail_result_step properties, and a test_id property when the test title contains [C123]-style case ids, so trcli parse_junit imports it directly.