🛠️ Tuist Run Report 🛠️
Builds 🔨
| Scheme | Status | Duration | Commit |
|---|---|---|---|
| TuistAcceptanceTests | ✅ | 4m 36s | d45e878cf |
| TuistUnitTests | ✅ | 5m 20s | d45e878cf |
Hive
GitHub issue · Closed
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.
git diff --check| Scheme | Status | Duration | Commit |
|---|---|---|---|
| TuistAcceptanceTests | ✅ | 4m 36s | d45e878cf |
| TuistUnitTests | ✅ | 5m 20s | d45e878cf |