QATrax
View as Markdown

In short — from your code to the certificate

Where you start, the steps to take, where you end up. The shortest path to a CRA certificate.


Where you start

Your software, its automated tests, and a version you are about to ship.

Where you end up

A CRA certificate for that version: its requirements, its tests, its software bill of materials (SBOM) and its known vulnerabilities, sealed and verifiable by anyone at qatrax.dev/verifier.

The five steps

1. Open your space — Create an account: a ten-day trial, no credit card.

2. Create your key — in your space: Projects tab, CI keys column. Keep it secret; it is valid for your project only.

3. Once: your requirements — Requirements tab. Three sources, to combine: the CRA catalogue (Annex I, Import button), your test plan (Dev+Test plan tab, Check and import button), or your ALM (Jira, Polarion: CSV or ReqIF). The plan links each requirement to the tests that prove it: without it, a test result received proves nothing.

4. At each version, one command — in your project (Node.js):

npm i -D @mostajs/mjs-unit @mostajs/mjs-sbom      # once
npx mjs-unit-menu                                  # then: 2 (SBOM) · 3 (test report) · 4 (send)

To send (choice 4), three variables: QATRAX_URL (the address of your space), QATRAX_CLE (your key), QATRAX_PROJET (your project's key). In continuous integration, the three in a row: npx mjs-unit-menu --choix=2 && npx mjs-unit-menu --choix=3 && npx mjs-unit-menu --choix=4. Java, C#, Python, C++, Go…? Your SBOM and your test tool's report are enough, as they are — JUnit XML, NUnit, TRX, TestNG, Robot Framework, CTest, Cucumber, Behave, Allure, CTRF or TAP: see QATrax without Node.js.

5. Issue — in your space: SBOM/Vulnerabilities tab, assess each one (affected, not affected, fixed); then the Deliverable tab → Issue and seal. The certificate is sealed.

Without a command line: through the interface, tab by tab

The tabs are at the top of every page of your space. First choose your project and the version you are shipping.

StepTabWhat you doButton
1. StartJourney (the first one)It shows the five steps of your version and what each one still lacks. Come back to it after each step.—
2. Set your requirements (once)Requirements — or directly CRA catalogue and Dev+Test planImport the CRA catalogue and your test plan: it says which test proves which requirement.Import · Check and import
3. Upload the test reportJourney, step ② — or the Runs tabChoose the file your tests produced: mjs-unit report or JSON report, JUnit XML, TAP, CTRF.Upload the results
4. Upload the SBOMJourney, step ③ — or the SBOM/Vulnerabilities tabChoose your SBOM file (CycloneDX or SPDX, JSON) and give the version.Upload the SBOM
5. Assess the vulnerabilitiesSBOM/Vulnerabilitiesqatrax has looked up the vulnerabilities of your SBOM. For each, choose: affected, not affected (with the reason) or fixed.—
6. Run the evaluationDeliverableqatrax gathers the requirements, tests, SBOM and vulnerabilities, then shows the verdict. Read it. If it suits you, issue.Issue and seal
7. Find the certificatesDeliverable, at the bottom of the page: the Issued deliverables listEach issued deliverable has its number, version and verdict. It downloads as a signed PDF, a sealed JSON and an HTML certificate, and can be verified.—
8. Have it signedSignaturesWith a signature bundle: tick the deliverables to be timestamped by the qualified provider, then confirm: one signature is deducted per deliverable. They come back under Signed.Send to the qualified provider

In short: Journey → Requirements → Runs → SBOM/Vulnerabilities → Deliverable. Each tab starts with a Help line that leads to the page of this documentation that explains it.

By default, the bar shows the tabs of these steps: Journey, Requirements, CRA catalogue, Runs, SBOM/Vulnerabilities, Deliverable, Technical file and Reports. The others (Manual tests, Signatures, Projects, Team, Dev+Test plan…) are under More ▾. To change where a tab goes (in the bar, under “More” or hidden) or their order: ⚙ Settings → Tabs, choose its place, drag them (or use ↑ ↓), then save. Default order restores the order; Reset everything to default also restores the bar and “More”.

The holder of the space sets the bar for the whole space; each team member can set their own, then go back to the space’s. What each person can change depends on their role on the project (Team → What each role can do): a viewer can only read.

Signature by a qualified provider. The PDF of step 7 is already signed and timestamped by qatrax. At step 8, you have it timestamped, in addition, by our qualified trust service provider (eIDAS), with your signature bundle. You choose which certificates to send; each sending deducts one signature, and a provider failure gives it back. Details: Signatures and bundles.

What to expect

VerdictWhat it means
Complianteverything is proven, no known exploitable vulnerability
Compliant with reservationsproven, but some points are to be completed (they are listed)
Non-complianta requirement is not proven, or a vulnerability is declared exploitable
Blockedan actively exploited vulnerability is to be assessed, or a piece does not match (tests altered, another SBOM)

A question? Write to us from your space.