CLINewv0.4.0
Import Allure results with qf
Qualflare's qf CLI now reads allure-results directories directly, so any framework with an Allure 2 adapter can send results, steps and retries to Qualflare.
If your tests already write Allure results, you can now send them to Qualflare unchanged. qf 0.4.0 reads an allure-results directory directly, so every framework with an Allure 2 adapter works with Qualflare, with no converter and no new reporter.
What's new
- Detected automatically.
qfrecognizes Allure output by what's inside the directory, not by its name. A single*-result.jsonfile works too. - Retries and flaky tests. Results that share an Allure history ID become attempts on one test. A test that failed and then passed, or that Allure marked flaky, is flagged as flaky.
- Your structure kept. Suites follow Allure's parent suite, suite and sub-suite. Labels, tags, links and nested steps come through, and Allure severities map to Qualflare's (blocker and critical become critical, trivial becomes info).
- Attachments. Screenshots, videos and Playwright traces upload as artifacts. Other files up to 1 MiB are attached directly.
- Parameters handled with care. Parameters marked hidden in Allure are dropped, and masked ones keep their name but not their value.
How to use it
pytest --alluredir=allure-results
qf myapp collect allure-results/
Availability
Requires qf 0.4.0 or newer. Upgrade with brew upgrade qualflare/tap/qf or npm install -g @qualflare/cli.