BuildPulse is a paid subscription product that connects to your CI provider — GitHub Actions, Jenkins, Buildkite, and others — through an action or SDK that uploads every build's test results to BuildPulse's servers. It builds a running dashboard of which tests have been flaky across your whole team's history, and can auto-quarantine the worst offenders so they stop blocking merges. Its free tier connects a repository and shows your flakiest tests starting from the first build, with paid plans priced by how many test results you send per day.
That is a genuinely useful job, and it is not this tool's job. This page parses the JUnit-XML reports you paste — nothing is uploaded, there is no account, and nothing is remembered once you close the tab.
| Question | Where to answer it |
|---|---|
| I have a failed run and its rerun right now — did the same test flip? | Flaky Test Finder — paste both reports, get a verdict in seconds, no signup, nothing leaves your device. |
| Which of our tests have been flaky across the last month of everyone's builds? | BuildPulse or a similar connected dashboard — that needs ongoing history across many builds, which a stateless browser page never collects. |
| I want flaky tests to stop blocking merges automatically, without anyone deciding case by case. | BuildPulse's quarantine feature — this tool only classifies what you paste; it does not touch your CI configuration or your test suite. |
| I don't want to connect my CI or send test data anywhere just to check one flip. | Flaky Test Finder — the browser page never makes a network request, and the CLI never phones home either. |
The two are not substitutes. A team that wants ongoing, historical, whole-organization flaky-test tracking with automatic quarantine needs a connected, always-on tool like BuildPulse — a page that only looks at whatever you paste into it, once, cannot do that job. A person staring at one red check who already has two reports and wants an answer before signing up for anything does not need a subscription or a CI integration to get it.
They answer the same underlying question — is this test flaky — for different situations. BuildPulse is a paid subscription product that connects to your CI provider (GitHub Actions, Jenkins, Buildkite, and others) via an action or SDK that uploads every build's test results to BuildPulse's servers, then builds a historical dashboard across your whole team and auto-quarantines the worst offenders so they stop blocking merges. It answers "which of our tests have been flaky over the last weeks or months, across everyone's builds", continuously, without you doing anything once it is connected. Flaky Test Finder is a free tool with no account and no connection: you paste two or more JUnit-XML reports you already have — say, a failed run and its rerun — and get a deterministic classification in your browser, right now, with nothing sent anywhere. It answers "did this specific test flip between these specific runs", once, for whoever is staring at a red check this minute. If you want an always-on team dashboard with history, BuildPulse's job is not one this page tries to do. If you have two reports in hand and want an answer before signing up for anything, that is what this tool is for.
No. There is nothing to connect and nothing to sign up for. The browser page parses the JUnit XML you paste entirely on your own device and never sends it anywhere; the CLI reads local files and makes no network call at all. BuildPulse's own public documentation describes the opposite model for its free tier: connect your repository and its GitHub Action uploads test results to BuildPulse so its dashboard can show your flakiest tests starting from the first build, which is a reasonable design for an always-on team tool, but it does mean your test result data leaves your infrastructure to reach BuildPulse's service.
Yes — continuous history across many builds and many contributors, automatic quarantine of flaky tests so they stop blocking merges without a person deciding case by case, and integrations with GitHub, Bitbucket, Jira, and Slack for a whole team's workflow, none of which a browser page with no server and no account can do. This tool has no memory between visits, quarantines nothing automatically, and only ever compares the specific reports you paste into it in that session.
No. This site is not affiliated with, endorsed by, or sponsored by BuildPulse. BuildPulse is named here only to describe what this tool is and is not, based on BuildPulse's own public pricing and documentation pages.
More: why tests go flaky in CI and what to do about each one.