running-tests

How to run tests in this repo. Read root AGENTS.md for always-on rules. Use ./test. Do not hand-roll tuist test or xcodebuild. Run checks in proportion to the change. Canonical flag list: ./test --help. Rationale for ./test over alternatives: header comment in test.

Documentation-only changes

Pure documentation or comment-only changes can skip ./test. Skip ./swiftformat --lint when the changed files are outside the formatter's scope. Record skipped checks and the reason in the commit or PR validation.

Do not classify a semantic change to configuration, scripts, generator inputs, executable examples, or app-rendered copy as documentation-only. Run the narrowest applicable checks below instead.

Pick a tier

Pick the narrowest tier that covers the change:

Tier	Command	When
Affected	./test	Default — bundles touched by your diff against origin/main
One bundle	./test WhereCoreTests	You know exactly what you touched
Unit suite	./test --all	Change spans modules; before a wide commit
Image suite	./test --snapshots	Triggers below
Everything	./test --everything	Full revalidation; what CI runs

Examples:

• Edited WhereCore only → ./test (or ./test WhereCoreTests if you want to be explicit)
• Edited WhereCore + WhereUI → ./test or ./test --all before committing
• Changed a stylesheet token that renders → ./test --snapshots (or ./test if the graph already pulls snapshots in)

Compare against a ref other than origin/main: ./test --base REF.

Architecture and host checks

Every normal invocation runs the complete Bumper Bowling sequence first. Use ./test --architecture-only to run only the configuration validation, rule tests, and architecture lint.

CI test jobs use --skip-architecture because the dedicated Bumper job owns that sequence. Do not use this flag for normal local validation.