xcbeautify is a little beautifier tool for xcodebuild.
Similar to xcpretty, but faster.
- 2x faster than
xcpretty. - Human-friendly and colored output.
- Supports the new build system's output.
- Supports Xcode's parallel testing output.
- Supports formatting Swift Package Manager output.
- Supports formatting Bazel output.
- Supports macOS & Linux.
- Written in Swift:
xcbeautifycompiles to a static binary which you can bring anywhere. This also means less Ruby-dependant in your development environment and CI.
Note: xcbeautify does not support generating JUnit or HTML test reports.
In fact, you shouldn't rely on xcodebuild's output to generate test reports.
We suggest using trainer or
XCTestHTMLReport to
generate test reports from xcodebuild's generated TestSummaries.plist
files.
xcbeautify uses itself to format its CI build logs.
If you use macOS 10.14.3 or earlier, install Swift 5 Runtime Support for Command Line Tools first:
brew cask install thii/swift-runtime/swift-runtimebrew install xcbeautifyswift brew install thii/xcbeautifymint install thii/xcbeautifypod 'xcbeautify'The xcbeautify binary will be installed at Pods/xcbeautify/xcbeautify
git clone https://github.com/thii/xcbeautify.git
cd xcbeautify
make installxcodebuild [flags] | xcbeautifyIf you want xcbeautify to exit with the same status code as xcodebuild
(e.g. on a CI):
set -o pipefail && xcodebuild [flags] | xcbeautifyFor parallel and concurrent destination testing, it helps to use unbuffered I/O for stdout and to redirect stderr to stdout.
NSUnbufferedIO=YES xcodebuild [flags] 2>&1 | xcbeautifyswift test [flags] 2>&1 | xcbeautifyParse Bazel's building and testing output:
set -o pipefail && bazel build //path/to/package:target 2>&1 | xcbeautifyset -o pipefail && bazel test //path/to/package:target 2>&1 | xcbeautify- Write more tests
Generate Xcode project:
make xcodeBuild with Bazel:
bazel build //Sources/xcbeautifyRelease a new version, say x.y.z:
make release version=x.y.zJust send a PR! We don't bite ;)
Don't have a GitHub account or prefer old-school patching via email? Send your patch to the project's mailing list.
MIT