DEMONSTRATION — fictitious data, no compliance value · read only
QATrax

Help: Nommer ses essais d’après le plan · Brancher sa CI

Dev+Test plan → traceability

Load a plan in mostajs-devtest/1 format (file docs/DEVTEST-PLAN.<module>.json). It is first read and checked (structure, enumerations, specRef resolved, coverage), then imported idempotently: re-importing the same plan updates, never duplicates. The project is created if needed from its key.

Export — get the plan as qatrax knows it today: DEVTEST-PLAN.tc200.json

Re-importing this file changes nothing (neutral round trip). What was entered in the UI with no linked requirement is not included — specRef is mandatory in the format.

— the content is copied below, nothing is sent before you confirm

— or paste the content —

From the command line: curl -b "$COOKIE" -H 'content-type: application/json' --data @docs/DEVTEST-PLAN.<module>.json https://demo.qatrax.dev/import

Import requirements from an ALM (Jira, Polarion, Jama…)

A CSV export (identifier and title columns; description and priority if present; separator guessed) or ReqIF (ReqIF.ForeignID, ReqIF.Name, ReqIF.Text). Missing requirements are added; an existing requirement has its title and description follow the ALM, never its status, which QATrax derives from the evidence.