feat(testing): Add default xcresult bundles for test tools#401
Merged
cameroncooke merged 1 commit intomainfrom May 7, 2026
Merged
feat(testing): Add default xcresult bundles for test tools#401cameroncooke merged 1 commit intomainfrom
cameroncooke merged 1 commit intomainfrom
Conversation
Create workspace-scoped result bundle paths for simulator, device, and macOS test commands when callers do not provide one. This makes test artifacts consistently available in text and structured output while preserving explicit result bundle paths. Extend workspace filesystem cleanup so managed result bundles are pruned safely without touching user-created bundles.
commit: |
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.
Create workspace-scoped default xcresult bundles for simulator, device, and macOS test tools when callers do not pass
-resultBundlePath.Previously, test artifact paths were only surfaced when xcodebuild reported a bundle path or the caller provided one explicitly. This makes the artifact path deterministic for agents and scripts, and keeps user-provided bundle paths unchanged.
The workspace filesystem lifecycle now recognizes XcodeBuildMCP-managed result bundles and prunes them safely, while protecting live bundles until their completion marker is written and leaving user-created bundles alone.