Less drudgery, more fun: using Kaleidoscope with XCTest failures
Most developers for Apple platforms deal with tests in some way or another. XCTest is probably the most popular framework because it’s built directly into Xcode and can be integrated with build processes and automation.
However, one problem with those tests is that more complex failures are not easy to interpret. And if things aren’t easy (and fun) to use, developers will have a resistance to using them. Wouldn’t it be nice if Kaleidoscope could show XCTest failures in a useful format?