История изменений

When a test crashes (e.g. force-unwrap of nil), Tuist now extracts the crash log from the xcresult bundle, parses it, and surfaces the stack trace directly in the test run dashboard. Each failure card shows the exception type, signal, and formatted crash thread frames so you can diagnose crashes without leaving your browser. The full .ips crash log is also available for download.

Additionally, the crash report is available in the CLI (tuist test case show <test-case-run-id>), which makes the crash report available to agents when for example fixing flaky tests.

Get notified via Slack when your app's bundle size increases significantly. Configure alert rules to monitor install or download size changes on a specific branch, and catch unexpected size regressions before they reach your users.

You can now attach custom metadata to your builds using environment variables. This includes both tags for categorization and key-value pairs for additional context like ticket numbers or CI runner information.

Use TUIST_BUILD_TAGS or TUIST_BUILD_TAG_* for tags, and TUIST_BUILD_VALUE_* for key-value pairs.

Filter your build analytics by tag in the dashboard:

View tags and custom values in the build detail page:

View all quarantined tests in your project at a glance. The new page shows analytics tracking the number of quarantined tests over time, and a searchable table with filtering options.

Track the complete history of state changes for each test case. The new Test History tab shows a timeline of events including when a test was first seen, when it was marked or unmarked as flaky, and when it was quarantined or unquarantined. Each event shows who made the change - whether it was done manually by a team member or automatically by Tuist.

Quarantine flaky tests to prevent them from blocking your CI pipeline. Tests can be automatically quarantined when marked as flaky, or manually quarantined from the test case detail page. Skip quarantined tests by running xcodebuild test $(tuist test case list --skip-testing).

Tuist now marks test cases as "New" when they haven't been seen in CI on your project's default branch before.

Flaky tests detected during your CI runs are now surfaced directly in Tuist's pull request comments. The new "Flaky Tests" section shows a summary of flaky tests per test scheme with a link to view all flaky runs. This makes it easier to spot and address flaky tests without leaving your pull request.

Get notified via Slack the moment a test becomes flaky. Configure alert rules to trigger when flaky runs exceed your threshold, and receive instant notifications with direct links to investigate the flaky test case.

Identify and track flaky tests in your CI pipelines. Tuist automatically detects flaky tests when the same test produces different results on the same commit across CI runs, or when using Xcode's test retries. Browse all flaky tests in the new Flaky Tests page, see flakiness rates on individual test cases, and track flaky runs over time.