- Home
- Test Flakiness Management Software
- FlakyWatch
FlakyWatch
What it is
FlakyWatch is a web service that monitors GitHub Actions test results, identifies unstable tests, estimates CI and developer time costs, and tracks flakes as GitHub issues. Users upload JUnit XML artifacts through a workflow step with the FlakyWatch GitHub App; the service says no agents or configuration files are required. It supports pytest, Jest, JUnit, RSpec, and other JUnit-compatible runners. Tests are classified as stable, flaky, broken, or newly unstable with confidence scores. Flaky tests can create GitHub issues containing classification, impact, and suggested next steps, and issues can reopen if the flake returns. Dashboard metrics include blocked runs, main failures, affected branches, and cost per test. An optional weekly email digest covers new unstable tests, cost trends, and open issues. The free plan costs nothing and covers one repository with 14-day history. Starter costs $29 a month for five repositories; Team costs $79 a month for 20. Slack integration is marked coming soon on Team.
For and against
For
- Supports several JUnit-compatible test runners
- Confidence-scored flaky-test classifications
- Automatic GitHub issue lifecycle
- Cost and impact dashboard metrics
- Free plan with weekly digest
Against
- Free plan limited to one repository
- Free history lasts 14 days
- Slack integration is coming soon
- Monthly subscriptions are non-refundable
The verdict
FlakyWatch connects GitHub Actions results with classification, cost reporting, and GitHub issue workflows. Check repository limits, retention periods, and the status of planned integrations before subscribing.
Who it suits
It suits development teams using GitHub Actions that want flaky-test classification, cost visibility, and issue tracking. The repository and history limits should guide plan selection.
Plans and prices
Free
1 repository · Classification + cost tracking · GitHub issue creation · 14-day history
Read 3 Oct 2026 · flakywatch.dev
Starter
5 repositories · Auto issue creation + lifecycle · Owner suggestions · 30-day history
Read 3 Oct 2026 · flakywatch.dev
Team
20 repositories · 90-day history · Quarantine rules · Slack integration (coming soon)
Read 3 Oct 2026 · flakywatch.dev
On the record
- Classification
- Tests are classified as stable, flaky, broken, or newly unstable, with confidence scores.flakywatch.dev · read 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 · read 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 · read 3 Oct 2026
- Integrations
- The site lists GitHub Actions and GitHub issues; Slack integration is marked coming soon on the Team plan.flakywatch.dev · read 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 · read 3 Oct 2026
- Reporting
- The dashboard includes impact metrics such as blocked runs, main failures, affected branches, and cost per test.flakywatch.dev · read 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 · read 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 · read 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 · read 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 · read 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 · read 3 Oct 2026
- Weekly digest
- FlakyWatch offers an opt-in weekly email digest with new unstable tests, cost trends, and open issues.flakywatch.dev · read 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 · read 3 Oct 2026
