Integrations
Framework Support
Qualflare's CLI auto-detects the results file your test runner already writes — no reporter package, no plugin, no per-framework setup. Point it at a results file and run one command.
Product news and testing tips.
Why it matters
One CLI, or a reporter per framework?
Most tools need a dedicated plugin or reporter package for every framework you run. A monorepo with Playwright, pytest, and Jest means three integrations to maintain.
Switching frameworks means starting over
Migrate from Selenium to Playwright and your reporting setup usually migrates with it — new config, new dashboards, new habits.
No single view across a multi-framework suite
E2E in Playwright, unit tests in Jest, security scans in Trivy — three tools, three reports, no combined picture of release health.
How it works
Emit results the way your framework already supports (JUnit XML, JSON, or a native reporter), then upload with the
same command regardless of framework: qf myapp collect results-file.
The CLI inspects the file and parses it automatically.
Also supported via JUnit-XML: Karate, Maestro, NUnit, MSTest, xUnit.net, Robot Framework.
What you get
Zero-config auto-detection
The CLI auto-detects the format of whatever results file your runner already writes — no reporter package or plugin to install for any framework.
23+ frameworks, one command
The same `qf collect` command works whether the results are JUnit XML, Playwright JSON, or a security scanner report.
JUnit-XML catch-all
Any framework that emits JUnit-compatible XML works out of the box — including NUnit, MSTest, xUnit.net, and Robot Framework, even without a named parser.
One dashboard across every framework
Results from every framework in a monorepo land in the same project, so pass rate, flaky tests, and defects are one picture, not five.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
- CI/CD Integrations
- All integrations
- Single pane of glass: unifying multi-framework results
- Monorepo test aggregation
Frequently asked questions
Which test frameworks does Qualflare support?
Qualflare's CLI auto-detects 23+ formats: JUnit, pytest, Go, Jest/Vitest, Mocha, RSpec, PHPUnit, TestNG, Cucumber, Karate, Playwright, Cypress, Selenium, TestCafe, Maestro, XCTest, Espresso, Newman, k6, OWASP ZAP, Trivy, Snyk, and SonarQube — plus any other JUnit-XML-compatible output, including NUnit, MSTest, xUnit.net, and Robot Framework.
Do I need to install a reporter plugin for my framework?
No. Qualflare ships no reporter package or plugin for any framework — the CLI uploads whatever results file your test runner already writes. Point it at the file and run `qf <project> collect <results-file>`.
Can I use multiple frameworks in the same project?
Yes — a common setup collects Playwright E2E results, Jest unit results, and a security scanner report into the same Qualflare project, so pass rate, flaky tests, and defects are one combined picture instead of three separate reports.
My framework isn't in the list — will it still work?
If it emits JUnit-compatible XML — which most CI-integrated test runners do — yes. Point the CLI at that file and it will parse without a dedicated integration.