Bring your own Mac.

Device evidence, on your infrastructure.

Xcode 27.1 beta includes the iPhone Duo SDK and simulator. It requires macOS Tahoe 26.6 or later. Confirm the Duo runtime is installed; no simulator test is marked passed without recorded execution.

Use an installed Apple-provided Xcode and simulator runtime. List available destinations using xcodebuild -showdestinations; use an actual installed destination, never an invented Duo identifier.

1. Use an isolated, disposable Mac VM for each repository. Xcode builds execute repository code.
2. Check out the exact commit shown in your source report.
3. Run the supplied mac-runner script with your project, scheme, simulator destination and result path. Use --test-plan for an existing plan and --only-testing to select your UI-test target.
4. Keep the xcresult bundle in your private CI artifacts. Review test count and failures.
5. Submit result metadata through the authenticated /api/runner/result endpoint. It verifies ownership and commit matching; results are labeled user-submitted evidence.

Recommended coverage

In the workspace’s Test coverage tab, download the plan for resize transitions, keyboard and safe areas, accessibility text, localization, scene isolation and Duo-specific behavior. Add those cases to your own UI-test target with stable accessibility identifiers and screen-by-screen accessibility audits.

What this does not prove

Passing an existing test suite does not imply hinge, multiple-display or Split View coverage. Add targeted UI tests for those behaviors. Device tests do not change the heuristic static score.