Ship faster with signal, not noise
Bitbucket Tests now automatically detects and quarantines flaky tests, cutting CI noise so your team can ship faster with confidence.
Flaky tests erode trust in your pipeline, waste CI minutes, and slow down deployments. What if your CI could spot and silence them automatically?
In January, we launched Tests in Bitbucket Pipelines—a new way to track, organize, and optimize tests right where your builds run. For the first time, teams could see test health over time, drill into failures, and quarantine noisy tests—all within their repo.
It was a big step forward. But manually triaging flaky tests across thousands of cases doesn’t scale.
Enter Automatic Flaky Test Detection.
Bitbucket now flags flaky tests automatically, so you spend less time firefighting and more time delivery customer value. With auto-quarantine, flaky failures stop blocking your builds the moment they’re caught.
What’s new: Flaky Test Detection, built-in
Building on the foundation of Bitbucket Tests, Bitbucket now automatically scans your test results and flags flaky tests—no extra scripts, plugins, or dashboards required. Just run your pipelines as usual, and Bitbucket does the rest:
- Spot flaky tests instantly: Bitbucket analyzes your test history and highlights unstable tests right in the UI.
- Keep your builds clean: Optionally, let Bitbucket auto-quarantine the noisiest tests so they stop blocking your team.
- Stay in control: Override any test’s status or execution strategy with a click.
Why it matters
Recent 2026 benchmarks published by Testdino reveal that 84% of pass-to-fail transitions in large-scale CI pipelines are caused by flakiness, while 30% to 60% of all full pipeline runs can fail due to this issue. Beyond compute costs, these tests incur high productivity losses—at Atlassian alone, an engineering analysis estimates 150,000 developer hours are wasted annually investigating flaky failures in a single major repository.
- Debug Faster: Stop chasing ghosts. Flaky tests are auto-flagged so you focus on real regressions—not reruns.
- Ship with Confidence: Fewer false reds. Fewer reruns. More time building—and momentum that lasts.
- Improve Build Reliability: Keep your signal clean. Quarantine flaky tests without losing track—fix them on your schedule. With automated detection and quarantine, teams spend less time rerunning builds and more time acting on real failures—turning CI from noise into reliable signal.
How it works
- Automatic detection is enabled by default for all Bitbucket Pipelines users on Standard and Premium plans.
- Flaky tests are flagged in the Tests tab, with a clear “Flakiness score” so you know what needs attention.
- Admins can fine-tune detection and auto-quarantine settings in repository settings.
Want the technical details? Check out our docs:
- Learn more and try Bitbucket Tests now
- Understand and manage flaky tests in Bitbucket Pipelines
- Quarantining flaky tests
What’s coming next?
We’re building a world where your test suite is a strategic asset, not a maintenance burden. Bitbucket Tests added clarity and automatic detection adds intelligence. More is coming—smarter analytics, AI insights, and deeper automation to help you ship faster with confidence.
Stay tuned—this is just the start. We’re investing in richer analytics and smarter automation to make managing tests a strategic advantage, not a chore.
Soon, features will identify and fix flaky tests, link pipeline failures to flaky tests for quick root cause analysis, and auto-optimize builds and tests.
Try it now—and help shape what’s next
Automatic flaky test detection is live in open beta for all Bitbucket Pipelines users. Give it a spin, and tell us what you think.
👉 [Open beta] Introducing Tests in Bitbucket Pipelines
Whether it’s feedback, feature requests, or bug reports—your input directly shapes the GA release and beyond. Let’s build the smartest CI experience together.