Skip to main content
Your CI pipeline runs automated tests and sends the report to Collabase. The results land in a cycle next to the manual ones.
You need an API token with the tests:write scope. Create it in your profile under Security.

Supported formats

A report can be up to 20 MB and hold up to 20,000 tests.

Send a report

Use buildId to name the run. A build that is sent in several parts uses shard and shardCount, and sending the same shard again is safe.

How tests are matched

For every reported test, Collabase looks for a case in this order. A case key in the test name, such as QA-T12 checkout works, wins. Next comes a name that was matched to a case before. If neither is found, the project rule decides: either a new case is created in an Imported folder, or the test waits in the list of tests without a case. Tests without a case appear on the Imports tab. For each one you can create a case, link it to the most likely case or ignore it.

When an import fails

The people who manage the project and the person who owns the token get a message with the format and a reason code. The import shows as failed on the Imports tab.

Next steps

Last modified on October 24, 2026