I have started to use XcodeBuildMCP to implement comprehensive end-to-end UI testing.

Unlike XCUITests, Claude can easily recover from flakiness, and I can install one version of the app, then update to another (on a different branch/worktree) to test for regressions and migration correctness.

I still have XCUITests for core flows on CI, but this is fantastic for comprehensive manual regression testing.

@ryanashcraft so you are just using it to bootstrap a build you want to test manually? I’ve been using it with Claude Code to create tests. Trying to determine if I’m missing a beneficial workflow.
@ryan it builds, installs, sets some user defaults and mutates the SQLite DB to set up the test. Then runs in Simulator, takes screenshots, analyzes the contents of screenshots to confirm expected text values, uses XcodeBuildMCP to interact with the Simulator and perform various actions - then repeats with a newer build to confirm no regressions. Records results in a markdown file. Repeats for 40+ different scenarios. All autonomous.