Trunk Flaky Tests
Trunk Flaky Tests identifies unreliable automated tests, tracks their failure patterns and helps prevent known intermittent failures from blocking CI pipelines.
Why it caught my attention
An automated test that fails unpredictably can hold up an entire release, even when the application works correctly. What makes Trunk interesting is its approach to separating unreliable test results from genuine failures, allowing development to continue while preserving the evidence needed to investigate and fix the underlying problems.
What problem does this actually solve?
Trunk Flaky Tests could be worth considering if you recognise any of these challenges.
Unnecessary test reruns waste time
Intermittent failures trigger repeated CI runs, consuming computing resources and delaying feedback without necessarily revealing application defects.
Unreliable results undermine developer confidence
When tests fail unpredictably, developers struggle to distinguish genuine regressions from failures caused by unstable tests.
Known failures delay software delivery
Quarantining identified flaky tests prevents their failures from repeatedly blocking CI while the tests continue running.
Intermittent failures are difficult to investigate
Historical results, failure patterns and stack traces help teams identify recurring issues that individual CI logs might obscure.
Is this a good fit for you?
A quick way to see if Trunk Flaky Tests is relevant for your situation.
- Your automated tests sometimes fail without corresponding application changes.
- Your team spends significant time rerunning failed CI jobs.
- You need to distinguish intermittent failures from genuine software regressions.
- You want to quarantine unstable tests without removing them from execution.
- You need historical evidence to prioritise and track test repairs.
- Your automated tests already produce consistently dependable results.
- You primarily need a framework for writing or executing automated tests.
How does it work?
In practice, the workflow looks something like this:
Configure Trunk to receive test results from your supported testing framework and CI environment, using the appropriate integration method.
As tests run, Trunk builds execution histories and identifies inconsistent outcomes, helping distinguish flaky tests from consistently failing ones.
Enable manual or automatic quarantining so recognised flaky failures no longer fail supported CI workflows, while affected tests continue executing.
Review failure histories and stack traces, then use supported ticketing integrations to organise investigation and track corrective work.
Monitor subsequent executions to confirm tests behave consistently, then remove quarantine when their results are dependable again.
What else should I know?
A few important things to be aware of before you investigate further.
Quarantine is not a repair
Quarantined tests still execute, but their failures may not block CI; teams must actively investigate and resolve them.
Integration requires suitable test reporting
Check your framework's reporting format and CI integration requirements; broad compatibility does not mean every setup works without configuration.
Usage limits and commercial terms
Published plans include test-span allowances and committer limits; confirm current pricing, entitlements and expected reporting volume.
Deployment and data residency options
The hosted service lists US data residency; enterprise deployment in a customer's environment is advertised as private preview.
Think Trunk Flaky Tests could fit your environment?
Visit the Trunk website to find out more, request a demo or speak to their team.
Something you'd like to know about Trunk Flaky Tests?
Is there something I haven't covered in my research? Send me your question and I'll look into it and reply personally by email.