QATrax
View as Markdown

Connect your CI

Create a CI key, then push the plan, test results and SBOM at each build.


The CI key

In your space: Projects → CI keys. A key is valid only for its project and for the chosen operations (pousser, emettre). It is passed in the header Authorization: Bearer <key>. It is shown only once; store it in your CI's secrets. It can be revoked at any time.

What the CI pushes

whatrequestbody
the Dev+Test plan (requirements, implementations, tests)POST /importJSON of the plan
the test resultsPOST /runs?p=<project>&format=jsonthe tool's report, as it is: JUnit XML, NUnit, TRX, TestNG, Robot, CTest, Cucumber, Behave, Allure, CTRF, TAP or JSON — see Test results format
the SBOMPOST /sbom?p=<project>&version=<product version>CycloneDX or SPDX (JSON)

See the recipes for GitHub Actions and GitLab CI, and the API reference.

What QATrax refuses

An SBOM without a product version, a file that is not an SBOM, a project the key does not cover: the response says why, in JSON. Accepting "to be helpful" would produce a file that looks compliant and is not.