xcbeautify is a little beautifier tool for
xcpretty, but faster.
xcbeautifycompiles to a static binary which you can bring anywhere. This also means less Ruby-dependant in your development environment and CI.
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
generate test reports from
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-runtime
brew install xcbeautify
swift brew install thii/xcbeautify
mint install thii/xcbeautify
xcbeautify binary will be installed at
git clone https://github.com/thii/xcbeautify.git cd xcbeautify make install
xcodebuild [flags] | xcbeautify
If you want
xcbeautify to exit with the same status code as
(e.g. on a CI):
set -o pipefail && xcodebuild [flags] | xcbeautify
For 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 | xcbeautify
swift test [flags] 2>&1 | xcbeautify
Parse Bazel's building and testing output:
set -o pipefail && bazel build //path/to/package:target 2>&1 | xcbeautify
set -o pipefail && bazel test //path/to/package:target 2>&1 | xcbeautify
Generate Xcode project:
Build with Bazel:
bazel build //Sources/xcbeautify
Release a new version, say
make release version=x.y.z
Just 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.
|Last commit: 2 weeks ago|
Release binaries for all platforms.