“### 6. Cloud — Best for Cypress-specific flakiness analytics Cypress Cloud”
“If Cypress is your primary automation framework, this deserves consideration.”
“- Number of flaky tests over time.”
“- Overall project flakiness.”
“- Flakiness severity.”
“- Filterable lists of flaky tests.”
“- Historical reliability comparisons.”
“Why it stands out: It gives you a project-level view of test reliability rather than making you investigate every failed execution individually. Flake analytics are available on the Team plan.”
“Pass-rate trends | ✅ | ✅ | ✅ | ✅ | ✅ | Partial”
“Failure-rate trends | ✅ | ✅ | ✅ | ✅ | ✅ | Partial”
“Failure categorisation | Limited | ✅ | ✅ | ✅ | Available | Limited”
“Self-hosted option | No | Available options | No | ✅ | ✅ | No”
“### 2. — Best for detailed test-suite analytics Currents”
“Particularly interesting if you're working with Playwright or Cypress.”
“- Flakiness rate and flakiness trends.”
“- Test failure rates over time.”
“- Pass/fail execution trends.”
“- Test duration and performance regressions.”
“- Individual test and spec-file health.”
“- Scheduled reports highlighting negative changes.”
“- Failure categorisation across multiple executions.”
“Why it stands out: Its Test Explorer provides actual trend comparisons, including whether an individual test's failure or flakiness rate is getting worse.”
“- Currents is particularly compelling if you want detailed test-level analytics, historical comparisons and automated regression reports.”
“### 4. — Best for failure analysis and historical reporting ReportPortal”
“A strong option if you want a centralised test analytics platform, particularly for larger QA teams.”
“- Passing-rate summaries.”
“- Flaky-test identification.”
“- Most frequently failing test cases.”
“- Failed-test trends over time.”
“- Execution duration history.”
“- Failure clustering and pattern analysis.”
“- AI-assisted failure categorisation.”
“Why it stands out: Rather than simply showing failed tests, it helps group failures into recurring patterns. It also supports self-hosted deployments.”
“Why it stands out: Rather than simply showing failed tests, it helps group failures into recurring patterns. It also supports self-hosted deployments.”
“### 1. — Best for pass-rate and flakiness trends BuildPulse”
“One of the closest matches to your requirements.”
“- Tracks pass rates over time.”
“- Identifies flaky tests and their historical behaviour.”
“- Measures flaky-test disruption and engineering impact.”
“- Shows 7-, 30- and 90-day trends.”
“- Highlights the tests responsible for the most disruption.”
“- Provides repository-level engineering metrics.”
“- Supports GitHub Actions, Bitbucket Pipelines and other CI systems through its reporting API.”
“Why it stands out: It doesn't just tell you that a test failed. It helps quantify how much instability that test introduces into your CI pipeline.”
“- BuildPulse is particularly compelling if you want engineering-level metrics and a straightforward picture of CI reliability.”
“Failure categorisation | Limited”
“Self-hosted option | No”
“### 3. — Best for enterprise test observability Datadog CI Visibility”
“Datadog goes beyond traditional test reporting.”
“- Flaky-test identification across commits.”
“- Historical failure rates.”
“- First and last occurrence of flakiness.”
“- Flakiness trend visualisation.”
“- Test execution performance.”
“- Correlation with CI pipelines and application observability data.”
“Why it stands out: You can investigate test failures alongside logs, traces and infrastructure telemetry. This is particularly useful when failures are caused by environmental instability rather than actual application defects.”
“Self-hosted option | No”
“### 5. — Best for test management plus analytics Allure TestOps”
“- Test case history.”
“- Reporting across test plans and projects.”
“Allure is worth considering if you want test management and test reporting in one place.”
“- Historical test execution results.”
“- Flaky and unstable test identification.”
“- Test execution statistics.”
“- Test launch comparisons.”
“One particularly useful feature is its unstable-test detection: it identifies tests with repeated status transitions across recent executions.”