Repository navigation
Expose .xctestrun files to test pre-actions - #3105
Draft
brentleyjones wants to merge 1 commit into
Draft
brentleyjones wants to merge 1 commit into
brentleyjones wants to merge 1 commit into
Conversation
brentleyjones
force-pushed
the
bj/expose-xctestrun-to-pre-actions
branch
from
October 19, 2026 19:01
4276fbf to
9720b67
Compare
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
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.
Pre-actions currently run before the
.xctestrunfile is generated, so they cannot adjust the prepared test configuration beforexcodebuildlaunches.Run the pre-action after generating the file and pass its path in
TEST_XCTESTRUN_FILE. The hook can then update environment variables, arguments, or other XCTest settings. It still receivesSIMULATOR_UDIDand runs once on either execution path;TEST_XCTESTRUN_FILEis only supplied when usingxcodebuild.Validation:
buildifierformatting and lint checks passed.--override_module=rules_apple=.... They exercise edits to the generated test environment and arguments, verify the hook runs once with the simulator ID, and cover directxctestexecution. Simulator and Xcode commands are stubbed in these tests.bazel run //doc:update;bazel test //doc:check_iospassed.