xcbeautify
xcbeautify copied to clipboard
cpisciotta
A little beautifier tool for xcodebuild
We have thousands of tests and it's very difficult to see which one(s) failed when we encounter a failure. A summary at the end of the output with these failed...
## Problem Errors in Storyboards are swallowed by xcbeautify. (I am use with Xcode12.4). For example: `error: Did not find view controller with identifier "AccountPoint" in Home.storyboard, referenced from Dashboard.storyboard`...
Xcode supports more stuff to performance test than just "wall clock time", it would be cool to also see those in the formatted output https://indiestack.com/2018/02/xcodes-secret-performance-tests/
My project in xcode14 would build with some error like this: ``` ❌ error: Dependency for P1:target-MyApp-fce55c0e14fedcc57d73ec039f604d040bdc1e3e5eb2ad770e53e15b1d5e91df-:Ad-Hoc-Mirror:SwiftDriver Compilation Requirements xiaoheihe normal arm64 com.apple.xcode.tools.swift.compiler is not absolute (Pods/Headers/Public/ActionSheetPicker_3_0/ActionSheetPicker-3.0.modulemap). (in target 'MyApp'...
Currently `xcbeautify` (with the GitHub Actions parser) parses errors inline where they occur. This makes it difficult to get a quick summary of the failed cases and reasons, like what...
