Freedom251 › Test Flakiness Management Software
FlakyWatch
What FlakyWatch is
FlakyWatch helps teams using GitHub Actions find and manage unreliable tests. Upload JUnit XML test results through a workflow step, and it classifies tests as stable, flaky, broken, or newly unstable, with confidence scores. It supports pytest, Jest, JUnit, RSpec, and other JUnit-compatible runners. The dashboard tracks blocked runs, main failures, affected branches, and cost per test, estimating the CI and developer time spent on flaky tests.
Flaky tests can be turned into GitHub issues containing their classification, impact, and recommended next steps; an issue can be reopened if the test becomes flaky again. An optional weekly email digest summarizes newly unstable tests, cost trends, and open issues. Setup uses the FlakyWatch GitHub App and a workflow step to upload results, with no agents or config files required. Its listed integrations are GitHub Actions and GitHub issues; Slack integration is marked as coming soon on Team.
The web service has a free plan for one repository and 14-day history. Starter is $29 a month for five repositories and 30-day history. Team is $79 a month for 20 repositories and 90-day history, with quarantine rules and priority support. Test execution data is retained for 30 days by default; aggregated statistics are retained for 14 days on Free and 90 days on paid plans.
Who it suits
FlakyWatch suits software teams running automated tests in GitHub Actions that want to identify flaky tests and follow their impact over time. It can also suit teams that want flaky tests tracked as GitHub issues and need repository limits or longer history available through paid plans.
What it does well
- Classifies tests with confidence scores across four statuses.
- Supports pytest, Jest, JUnit, RSpec, and compatible runners.
- Tracks blocked runs, failures, branches, and cost per test.
- Can create and reopen GitHub issues for flaky tests.
- Optional weekly digest covers unstable tests, costs, and open issues.
What to know first
- Free plan is limited to one repository and 14-day history.
- Starter is limited to five repositories and 30-day history.
- Slack and CSV export on Team are marked coming soon.
Limits
The free plan allows one repository and 14-day history. Starter covers five repositories and 30-day history; Team covers 20 repositories and 90-day history. Aggregated statistics are retained for 14 days on Free and 90 days on paid plans.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Free | forever · 1 repository · Classification + cost tracking · GitHub issue creation · 14-day history · Weekly digest | Free |
| Starter | monthly · 5 repositories · Auto issue creation + lifecycle · Owner suggestions · 30-day history · Email support | $29 a month |
| Team | monthly · 20 repositories · 90-day history · Quarantine rules · Slack integration (coming soon) · CSV export (coming soon) · Priority support | $79 a month |
As flakywatch.dev lists them, read 3 Oct 2026. The maker's own page has the final word.
Getting started
- Open the FlakyWatch website and choose a plan.
- Install the FlakyWatch GitHub App.
- Add a workflow step to upload JUnit XML artifacts.
- Use a supported JUnit-compatible test runner to provide results.
Verdict
Choose FlakyWatch if your team uses GitHub Actions and wants flaky test detection tied to cost metrics and GitHub issue tracking. Teams needing more than one repository or longer history must choose a paid plan; Slack and CSV export are not yet available on Team.
Questions
Is there a free plan?
Yes. Free costs nothing, billed forever, and includes one repository, classification and cost tracking, GitHub issue creation, 14-day history, and a weekly digest.
What do the paid plans cost?
Starter costs $29 a month, billed monthly. Team costs $79 a month, billed monthly.
Which platforms and test frameworks does it support?
FlakyWatch is web-based and monitors GitHub Actions results uploaded as JUnit XML. It names pytest, Jest, JUnit, RSpec, and JUnit-compatible runners as supported.
Which integrations are available?
The listed integrations are GitHub Actions and GitHub issues. Slack integration is marked as coming soon on Team.
Does FlakyWatch access source code?
Its privacy policy says it accesses repository metadata, workflow run data, uploaded JUnit XML, commit SHAs, branch names, and run timestamps, but not source code or other repository files.
How long is data retained?
Test execution data is retained for 30 days by default. Aggregated statistics are retained for 14 days on Free and 90 days on paid plans.
Facts from FlakyWatch's own pages
- Classification
- Tests are classified as stable, flaky, broken, or newly unstable, with confidence scores. · flakywatch.dev, 3 Oct 2026
- Data access
- The privacy policy says FlakyWatch accesses repository metadata, GitHub Actions workflow run data, uploaded JUnit XML artifacts, commit SHAs, branch names, and run timestamps, but not source code or other repository files. · flakywatch.dev, 3 Oct 2026
- Data retention
- Test execution data is retained for 30 days by default; aggregated statistics are retained for 90 days on paid plans and 14 days on the free plan. · flakywatch.dev, 3 Oct 2026
- Integrations
- The site lists GitHub Actions and GitHub issues; Slack integration is marked coming soon on the Team plan. · flakywatch.dev, 3 Oct 2026
- Issue tracking
- Flaky tests can become GitHub issues with classification, impact, and recommended next steps; issues can be reopened if the flake returns. · flakywatch.dev, 3 Oct 2026
- Reporting
- The dashboard includes impact metrics such as blocked runs, main failures, affected branches, and cost per test. · flakywatch.dev, 3 Oct 2026
- Security
- The privacy policy states that data is encrypted in transit and at rest, production systems have access controls, and the service uses least-privilege access and regular security audits. · flakywatch.dev, 3 Oct 2026
- Service limits
- The terms state that the free plan is limited to one repository and 14-day data history, and that monthly subscriptions are non-refundable. · flakywatch.dev, 3 Oct 2026
- Setup
- The site says setup uses the FlakyWatch GitHub App and a workflow step to upload JUnit XML artifacts, with no agents or config files required. · flakywatch.dev, 3 Oct 2026
- Support
- FlakyWatch lists email support on Starter, priority support on Team, and says it aims to respond to inquiries within 48 hours during business days. · flakywatch.dev, 3 Oct 2026
- Test results
- Users upload JUnit XML results from GitHub Actions; the site names pytest, Jest, JUnit, RSpec, and any JUnit-compatible runner as supported. · flakywatch.dev, 3 Oct 2026
- Weekly digest
- FlakyWatch offers an opt-in weekly email digest with new unstable tests, cost trends, and open issues. · flakywatch.dev, 3 Oct 2026
- What it does
- FlakyWatch monitors GitHub Actions test results, detects and classifies flaky tests, estimates CI and developer time costs, and tracks them as GitHub issues. · flakywatch.dev, 3 Oct 2026
Where FlakyWatch stands on Freedom251
- Test Flakiness Management Software#16 of 31