Flaky Test Quarantining is Now Available
Following up on our initial announcement, test quarantining is now live!
Quick recap of what you can now do:
- Detect flaky tests automatically via retries or cross-run analysis
- Quarantine them so they stop blocking PRs while you fix the root cause
- Get notified in Slack and GitHub PR comments when flaky tests appear
Quarantining in action
When you quarantine a test, it gets excluded from your CI runs entirely. You can enable automatic quarantine in your project’s Automations settings (newly detected flaky tests get isolated immediately), or manually quarantine specific tests from the test case detail page.
To skip quarantined tests in CI:
xcodebuild test \
-scheme MyScheme \
$(tuist test case list --skip-testing)
Once you’ve fixed the underlying issue, unmark the test as flaky. If it becomes flaky again, Tuist will detect it and notify you.
Blog post
We wrote up a deeper dive on why flaky tests matter (especially with AI coding agents generating more PRs), how detection works, and how to integrate quarantining into your workflow: Stop Flaky Tests from Blocking Your PRs
What’s next
We’re looking at issue tracker integration (auto-create issues when flaky tests are detected) and test sharding. Let us know what would be most useful for you!