Report from your CI pipeline

Generate a JUnit XML or Mochawesome JSON result file with your test runner, then publish it with tc report.

Report to an existing plan

export TESTCOLLAB_TOKEN='your-api-token'

tc report --project 123 --test-plan-id 456 \
  --format junit --result-file ./results/junit.xml

The plan must contain the cases you intend to report. Use recognizable case references in the result file and inspect unmatched-case messages before relying on the summary.

Let the CLI prepare a plan

For workflows that should create their own plan and missing repository assets, opt in explicitly:

tc report --project 123 --auto-create \
  --build 2.4.0-rc.1 --environment staging \
  --format junit --result-file ./results/junit.xml

--auto-create can create records. Test the mapping in a project intended for your integration before adding it to a production pipeline.

Add a quality gate

Run the gate against the plan created or selected by your workflow:

tc gate --project 123 --test-plan-id 456 \
  --fail-on failed,blocked --require-complete --min-pass-rate 95

A gate can fail with a nonzero exit status. Preserve that exit code in your CI job so the pipeline reflects the result.

Keep the report even when tests fail

Configure your CI system to run the reporting step after test execution, including failed test runs. Upload the actual result file and keep its build/run context. A failed test process should not prevent the team from seeing the evidence.

For BDD-managed cases, sync the feature definitions and use stable scenario references. The CLI can preserve synced scenario ownership instead of creating ordinary duplicates.