Tuist

Tuist

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

Product

Build scans now include machine-level performance charts for CPU, memory, network, and disk usage. See exactly what your build machine was doing during the build to spot resource bottlenecks. Available for both Xcode and Gradle builds. For Xcode, run tuist setup insights to enable metric collection. Gradle builds collect metrics automatically through the plugin.

Machine metrics charts

Product

Gradle build details now show the tasks that were explicitly requested by the user (e.g., assembleRelease, connectedAndroidTest), making it easy to distinguish between different build types in CI environments with multiple builds.

Gradle build details with requested tasks

Product

Block pull requests when your app's bundle size grows beyond a configured limit. Tuist automatically creates GitHub Check Runs that compare the install or download size against a baseline branch. If the threshold is exceeded, you can accept the increase directly from the GitHub UI. Learn more in the bundle insights documentation.

Bundle size thresholds settings

Product

See attachments associated with a given test case run directly in the dashboard to understand why your tests might have failed as quickly as possible.

Test case run detail page showing image attachments from a snapshot test failure

Product

You can now click on any test case run to open a dedicated detail page with everything you need to understand what happened in that run.

Test case run detail page showing overview with run details and flaky runs

Product

Tuist now supports the Model Context Protocol (MCP) over HTTP so coding agents can authenticate and interact with your Tuist data directly.

This first release includes:

  • OAuth discovery and dynamic client registration for MCP clients.
  • A protected MCP endpoint at /mcp with proper bearer challenges.
  • Initial tools for test analysis workflows:
    • list_projects
    • list_test_cases (with optional flaky filter)
    • get_test_case
    • get_test_run
    • get_test_case_run
  • An initial prompt (fix_flaky_test) that guides agents through diagnosing and fixing flaky tests.

This gives agents enough context and tooling to inspect flaky tests and drill down into run-level failure details from Tuist.

Product

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.

Crash report in test run dashboard

Product

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.

Bundle size alert rule configuration

Product

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:

Build insights with tag filtering

View tags and custom values in the build detail page:

Build detail with tags and custom metadata

Product

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.

Quarantined tests page showing analytics chart and list of quarantined tests