docs: skip the UI tests in the default local test command - #140
Merged
Conversation
The documented build-and-test command ran every target, so agents and contributors following it drove the app through the full UI suite on each change. That needs an unlocked display and takes minutes, and CI already runs those tests on every PR. The default now skips the UI test target, and the UI test command is framed as the deliberate opt-in for iterating on those tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AGENTS.mdgavexcodebuild clean analyze testas the command to run, and plaintestruns every target in the scheme. Anyone following it — a person or an agent — drove the app through the full UI suite on every change, which needs an unlocked display and takes a couple of minutes.CI runs the unmodified full
teston every PR (.github/workflows/ci.yml:31), so the UI tests keep their coverage. This only changes what gets run locally by default.Changes
The default command now passes
-skip-testing:"Front Row UI Tests", and the UI test command is reframed from "while iterating on them" to the deliberate opt-in:-skip-testingrather than-only-testing:"Front Row Tests"so that a future test target is picked up locally without anyone having to remember to update this file.Testing
Ran the new default command:
** TEST SUCCEEDED **. The full Swift Testing unit suite runs and passes, no app window is launched, and it finishes in roughly 30 seconds instead of two and a half minutes.Documentation only — no source changes.