更新日誌

Account settings now shows your global Kura endpoint when it is available, making it easier to point clients at the nearest healthy region without copying regional endpoints one by one.

Register HTTPS endpoints on your account, pick the Tuist events each one should listen to, and have downstream systems react the moment a test case is created or updated, or a preview is created or deleted — post fresh builds into Jira, mirror flaky-test transitions into your incident tracker, no polling required.

Test case timelines now show exact timestamps when you hover over relative dates. This makes it easier to compare when a test was marked flaky, muted, skipped, or first seen against the runs around it without leaving the dashboard.

The tooltip is available in both the Test History tab and the compact history section on the test case overview.

You can now build automations that react to individual test case changes the moment they happen, instead of waiting for the scheduled flakiness monitors to converge. Pick Test updated under When and tick the changes you care about — Marked as flaky, Unmarked as flaky, or state transitions to Enabled / Muted / Skipped — and the configured actions fire right away. The common shape: someone manually marks a flaky test, the automation immediately mutes it and pings Slack. Each automation-driven change also lands on the test case timeline attributed back to the rule that triggered it, so you can always see which automation moved a test and why.

The Selective Testing tab on test run and run detail pages now has a Hit filter next to the search box, matching the existing Module Cache experience. Narrow the table to Local hits, Remote hits, or Misses to quickly see which test modules actually ran and which were skipped thanks to selective testing.

Automations now offer a rolling-window option alongside the calendar window. Pick Last days to evaluate over a fixed period like 30d, or Rolling window to evaluate over the last N runs of each test case — useful when test volume varies day-to-day and a fixed time window over- or under-reacts to recent activity. The same dropdown is wired into Recovery so you can wait either for X days or for N new runs without a re-trigger before recovery actions fire.

The analytics card on the Quarantined Tests page now splits the count into three widgets: total quarantined, Muted, and Skipped. Each widget has its own value, trend, and a chart that switches when you click it, so it is easier to see whether the suite is leaning on muted failures or actively excluding tests from execution. Selecting a widget pins the chart to that mode and persists the selection in the URL for sharing.

The Selective Testing tab on a test run now exposes the same per-target subhashes the Module Cache tab already had. Expand a row to see exactly which inputs went into the hash — sources, dependencies, environment variables, project and target settings, Info.plist, and the rest — making it straightforward to pinpoint the input that drifted when a previously cached test target shows up as a miss. The card also gains a Copy as JSON action that snapshots every selective testing target with its hashes, ready to paste into a ticket or diff against another run.

Automations now have a Comparison dropdown alongside When, with Greater or equal, Greater than, Less than, and Less or equal. Pair it with a "Less than" comparison and an Unmark as flaky action to clean up stale flaky labels — including ones set manually or by an automation you've since removed — without touching tests that are still flaking.

Organizations can now use SCIM 2.0 to let identity providers such as Okta provision, update, and deprovision Tuist members automatically. Generate a SCIM bearer token from the Authentication settings page, configure your IdP with the SCIM endpoint URL, and assign users or groups from your IdP to keep Tuist membership in sync.

SCIM provisioning works alongside SSO: SCIM manages membership lifecycle, while SSO controls sign-in. Deprovisioned members are removed from the organization, preserving their user record and historical work without disabling access to other Tuist organizations.