René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add explicit build-for-testing action","articleBody":"## Summary\n\nPlease add an explicit XcodeBuildMCP action/CLI tool equivalent to `xcodebuild build-for-testing`.\n\n## Motivation\n\nToday, the CLI exposes build and test actions such as:\n\n```bash\nxcodebuildmcp simulator build\nxcodebuildmcp simulator test\nxcodebuildmcp device build\nxcodebuildmcp device test\nxcodebuildmcp macos build\nxcodebuildmcp macos test\n```\n\nFor simulator tests, XcodeBuildMCP already appears to use a two-phase flow internally when test preflight is available: `build-for-testing` followed by `test-without-building`. However, there does not appear to be a user-facing action that performs only the `build-for-testing` phase.\n\nThis is useful for workflows that want to prepare test bundles once and run tests later or elsewhere, mirroring existing `xcodebuild` workflows.\n\n## Requested behavior\n\nAdd a first-class action, for example:\n\n```bash\nxcodebuildmcp simulator build-for-testing\nxcodebuildmcp device build-for-testing\nxcodebuildmcp macos build-for-testing\n```\n\nor another naming scheme consistent with the project.\n\nThe action should pass through the same core options as the existing build/test commands, including project/workspace path, scheme, configuration, destination, derived data path, and extra xcodebuild args.\n\n## Notes\n\nPassing `build-for-testing` through `--extra-args` is not equivalent because the existing build command appends its own final `build` action. A dedicated action would make this behavior discoverable and avoid requiring users to fall back to raw `xcodebuild`.\n","author":{"url":"https://github.com/yqiang","@type":"Person","name":"yqiang"},"datePublished":"2026-06-19T21:09:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/450/XcodeBuildMCP/issues/450"}