Repository navigation
test(examples): Add app launch smoke test and PR workflow - #470
Merged
Merged
Conversation
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.
Add an iOS UI smoke test that builds and launches the examples app, checks that the Examples screen appears, and verifies that the app remains in the foreground without visible error UI. Run it through
make test-example-iosand a pull-request workflow that uploads diagnostics on failure.Verification
Passed
make test-example-ios IOS_SIMULATOR_OS=27.0,make test-macos,make lint, andgit diff --check. Commit hooks also validated the GitHub workflow. UI coverage is limited to iOS, and the workflow has not yet run on GitHub. Xcode/Simulator diagnostics remain, including XCTest deployment-version linker warnings from the initial build.Test framework
UI automation uses XCTest rather than the repository's Swift Testing convention because XCUITest requires it. The UI test target is declared in XcodeGen, as requested, rather than the Swift package manifest.