Test reporting for every framework

Qualflare turns your CI test results into hosted, historical reporting with AI analysis — whatever framework you run. Its CLI auto-detects 23+ frameworks, then clusters failures by root cause, scores flaky tests, and rates each launch’s risk. Below are step-by-step reporting guides for the most popular ones.

Framework reporting guides

• Playwright test reporting

  Send Playwright JSON results — AI failure clustering and flaky scoring from Playwright’s native retry data.

• pytest test reporting

  Upload pytest --junitxml output — AI clustering, history-based flaky detection, and pytest-xdist aggregation.

• Cypress test reporting

  Send Cypress JUnit or mochawesome results — AI clustering and flaky scoring from Cypress’s built-in retries.

• Jest test reporting

  Send Jest JSON results — AI failure clustering and history-based flaky detection across every CI run and monorepo package.

• JUnit (Java) test reporting

  Upload Java JUnit XML from Maven Surefire or Gradle — AI clustering, flaky detection from the XML, and multi-module aggregation.

Also works with Mocha, Selenium, Cucumber, TestNG, RSpec, k6, Newman and more — point the Qualflare CLI at your results file and it auto-detects the format.

How it works

Every guide follows the same two steps: have your test runner write a machine-readable results file (JSON or JUnit XML), then upload it with one CLI command — qf <project> collect <file>. The CLI attaches your Git branch and commit and turns each CI run into a tracked launch with AI failure clustering, flaky-test scoring, per-launch risk, and trends over time — the analysis a local HTML report can’t do.

Weighing platforms? See how Qualflare compares to other test management tools, read how to evaluate test observability platforms, or browse the best AI test management tools roundup.

Frequently asked questions