Hive Hive
Sign in

fix(cli): isolate acceptance fixtures from feature flags

GitHub issue · Closed

Metadata
Source
tuist/tuist #10993
Updated
Jun 26, 2026
Domains
CLI
Details

Resolves N/A

This isolates acceptance fixtures from ambient feature flag environment variables.

The canary cache acceptance tests intentionally mock their fixture environment, but the fixture trait was copying every outer environment variable back into the mocked environment. That allowed values like TUIST_FEATURE_FLAG_KURA from the outer tuist test wrapper to leak into nested fixture commands, so canary cache tests could unexpectedly request Kura endpoints even when the fixture itself did not opt into Kura.

This keeps the existing environment handoff behavior, but filters TUIST_FEATURE_FLAG_* at the fixture boundary. Tests that need a feature flag can still set it explicitly inside the fixture setup, while CI-level flags no longer change acceptance test behavior implicitly.

How to test locally

  • git diff --check
Comments
TA
tuist-atlas[bot] May 30, 2026

This pull request’s changes isolating acceptance fixtures from feature flags are now available in CLI 4.195.10. Update to this version to get the fix.