Compare Test Case

Quick Start

You'll typically receive a test case identifier and two branches. Follow these steps:

1. Run tuist test case show <id-or-identifier> --json to get the test case metrics.
2. Run tuist test case run list <identifier> --json to see runs across branches.
3. Compare behavior between base and head branches.
4. Inspect failures with tuist test case run show <run-id> --json.
5. Summarize findings with root cause analysis.

Step 1: Resolve the Test Case

By ID or dashboard URL

tuist test case show <test-case-id> --json

By identifier (Module/Suite/TestCase)

tuist test case show Module/Suite/TestCase --json

If no test case is provided

Discover flaky or failing tests to investigate:

tuist test case list --flaky --json --page-size 10

Key fields from the response:

• id -- unique identifier for subsequent commands
• name, module_name, suite_name -- the test identity
• reliability_rate -- percentage of successful runs
• flakiness_rate -- percentage of flaky runs in the last 30 days
• total_runs / failed_runs -- volume context
• is_flaky / is_quarantined -- current flags

Step 2: Get Runs on Each Branch

List test case runs filtered by the test case, and look at the git_branch field:

tuist test case run list <identifier> --json --page-size 20

Separate runs by branch. For each branch, compute:

• Pass rate: passed_runs / total_runs * 100
• Average duration
• Flaky run count
• Most recent status

Defaults

• If no base branch is provided, use the project's default branch (usually main).
• If no head branch is provided, detect the current git branch.

Step 3: Compare Branch Behavior