Tracking tests on non-default branches was one of the most requested capabilities during the Bitbucket Tests (beta). We heard you, and today, we’re shipping it.
Most teams don’t ship from main. Integration happens on develop, stabilisation on staging, releases cut from release. Until now, Bitbucket Tests only tracked the tests from default(main) branch, leaving the branches that actually matter invisible.
Multiple branch tracking in Tests changes that. Bitbucket Tests can now track up to 5 branches per repository including the default branch( often main), making failure rates, flaky scores, and test history reflect real delivery workflows.
Bitbucket Tests is available on the Standard and Premium plans.
Why it matters
- Test health where testing and releases happen. Integration, staging, and release branches are now first-class, not just the repository default.
- Flaky detection with full coverage. Failure rates and flaky scores aggregate across all tracked branches, surfacing the worst offenders wherever they fail. For more detail, read the earlier post on flaky test detection.
- Branch-specific answers. Every test execution shows its branch. A single filter isolates failures to one tracked branch.
Get started
1. Ensure your test frameworks in the pipelines are generating JUnit-Xml compatible test reports. If not already generating. Know more about Bitbucket Tests
2. Open Tests → Configure branch tracking (visible to repository admins)
3. Add the branches the team ships/tests from.
4. Results flow in from the next pipeline run.
Left: Summary of Test results
Right: Single test executions
See the branch tracking section of the Get started with tests in Pipelines help document for step-by-step guidance on configuring branch tracking and making the most of test insights across your delivery branches.
Share feedback
Multiple branch tracking was prioritised based on customer feedback, and we’d love to keep learning from you. Share your questions and ideas in the community thread to help shape what comes next.
