Skip to content

About

Concise build and test output for Xcode projects.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

11 Commits

Folders and files

Repository files navigation

xcode-tools

CI

Wrappers around xcodebuild that deduplicate build errors and report test failure reasons. A run is retried only while a concurrent build holds the build database.

Setup

Install Xcode with the required platform SDKs and simulators, select it with xcode-select, and install jq (brew install jq) for test-result parsing. Clone this repository and add its directory to your shell's PATH.

Usage

Run from the project directory with an existing Xcode scheme:

xcode-build MyApp                 # Debug
xcode-build MyApp Release
xcode-test MyMacApp
xcode-test MyApp -destination "platform=iOS Simulator,name=iPhone 18 Pro"
xcode-test MyApp --result-path ./results.xcresult
xcode-test MyApp -- -only-testing:MyAppTests/SomeTest

Without -destination, xcodebuild picks the destination; pass one for simulator runs.

Both commands accept -h/--help, -destination DEST, and extra xcodebuild flags after --. Only xcode-test accepts --result-path PATH; its default is $TMPDIR/<scheme>Test.xcresult (or /tmp when TMPDIR is unset). The existing result bundle at that path is replaced on each run.

Successful test runs print aggregate test counts, deduplicated build/runtime warnings, and the result-bundle path. Counts follow xcresulttool's test summary; parameterized executions can outnumber the reported tests. Warning output is limited to five messages, with long messages shortened; inspect the bundle for complete diagnostics. If result metadata cannot be read, the output says so and falls back to console warnings. A passing test suite can still report a coverage collection failure.

MIT license.

About

Concise build and test output for Xcode projects.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages