ReportersNewv0.1.19
CTRF support: upload and export Common Test Report Format
Qualflare now reads and writes CTRF, the Common Test Report Format: upload CTRF from any tool with qf or the API, and export any launch back as CTRF.
Qualflare now supports CTRF, the Common Test Report Format: an open JSON format that many test frameworks and CI tools can produce. Any tool that writes CTRF can now send its results to Qualflare, and any Qualflare launch can be exported back as CTRF.
What's new
- Upload CTRF with
qf.qf <project> collect results.jsonrecognizes CTRF files automatically, in both the current and the older layout. - Upload CTRF with the API. Send a report to
POST /api/v1/collect/ctrfwith your project access token, no CLI needed. - Export a launch as CTRF.
GET /api/v1/launch/{launchSeq}/ctrfreturns the whole launch as a CTRF report, so you can feed your results into other tools. - Seven statuses, nothing lost. Qualflare keeps all seven test statuses (passed, failed, skipped, error, timeout, aborted and pending) instead of merging timeout and aborted into failed or error. On export these appear as
failed, with the exact status inrawStatus, so uploading the export again restores them. - Retries count toward flakiness. CTRF retry attempts become per-attempt history, which Qualflare uses to detect flaky tests.
Availability
Requires qf 0.1.19 or newer for CLI uploads. CTRF upload and export work on every plan. Exports are limited to launches with fewer than 20,000 case results.