Quarantined tests now have two modes: Muted (runs, failures masked, the existing behaviour) and Skipped (excluded from execution; xcodebuild gets -skip-testing and the Gradle plugin filters with excludeTestsMatching). Pick the mode from the test case dropdown, filter by it on the Quarantined Tests page, or have an automation set it for you.
The Test Cases page has a new "Test cases" widget that plots the number of distinct test cases with at least one run in the preceding 14 days. The Flaky Tests page has a matching "Flaky Tests" widget that plots the number of tests currently flagged as flaky over time, alongside the existing "Flaky Runs" metric. Click either widget to swap the chart.
Flaky-test handling used to be a fixed set of project toggles: auto-quarantine on or off, one threshold, one cooldown, one Slack channel. That made every team fit the same mould. Automations let you decide what "flaky enough to act on" means for your project, and what should happen when a test crosses that line — quarantine it, keep it green but flag it, ping a specific channel, or any combination — and how it should recover on its own. The engine is built to grow beyond flaky tests, so the same shape will cover more of your test-suite hygiene over time.
Test run details now show every device or simulator the run executed on, alongside the existing Mac host info. For multi-destination test plans, each destination is listed with its platform and OS version so you can see at a glance whether tests ran on iPhone, iPad, Apple TV, Apple Watch, or Vision Pro.
When HTTPS_PROXY or HTTP_PROXY is set in the environment, Tuist now automatically routes the HTTP connections it manages (cache, previews, analytics, registry access, and the calls the Gradle plugin makes back to Tuist services) through that proxy. Nothing to configure: the CLI and Gradle plugin pick up the variable and use it.
Analytics dashboards now offer a scatter plot view alongside the existing line charts. Toggle between Line and Scatter plot to see individual data points for build durations, test run durations, cache hit rates, and selective testing effectiveness. Use the Group by dropdown to color dots by scheme, environment, or category. Click any dot to jump straight to the detail page.
Tuist now supports parameterized tests from Swift Testing (@Test(arguments:)). Each argument variant is tracked individually with its own status, failures, and attachments, giving you per-argument visibility into what passed and what failed.
The dashboard now adopts the authenticated user's browser language automatically when a matching dashboard locale is available. It currently recognizes English, Spanish, Japanese, Korean, Russian, Cantonese, Simplified Chinese, and Traditional Chinese.
You can now configure how long a test must go without a flaky occurrence before its flaky flag is automatically cleared. Previously this was fixed at 14 days. Head to your project's Automations settings to set the Cooldown period to a value that works for your team.
Tuist's pull request comments now show which specific tests failed, including the failure message and a link to the source file in GitHub. This lets you identify and fix failures directly from the PR without opening the dashboard.