Subliminal

At the other end of the spectrum, there's Subliminal[1], which relies on Apple's UIAutomation underneath, which in turn relies on the application's accessibility information as-is, rather than hijacking it. Building up tests using either UIAutomation or something that sits on top of it like Subliminal will actually help you improve your app's accessibility at the same time. [1] https://github.com/inkling/subliminal

I think that Github now labels them as "collaborators" in the UI. In this PR for example, wearhere is labelled as a collaborator in the corner of his comment. https://github.com/inkling/Subliminal/pull/170

Yes. You can send Javascript to be evaluated by UIAutomation so it has all the capabilities of that UIAutomation does. There's a PR that adds this natively https://github.com/inkling/Subliminal/pull/118, but you can also just implement it yourself quite easily: - (void)captureScreenshotWithFilename:(NSString *)filename { [[SLTerminal sharedTerminal] evalWithFormat:@"UIATarget.localTarget().captureScreenWithName(\"%@\")", [filename slStringByEscapingForJavaScriptLiteral]]; }

My personal recommendation on Automated Testing is to use Subliminal https://github.com/inkling/Subliminal Subliminal allows you to write tests in Objective-C that interface directly with your app. This makes your tests be more powerful (can test things not visible to the user, and can simulate activity that UIAutomation can't (like a credit card swipe, which is why KIF was invented)). More amazing is that you get the benefits of static typing. Instead of stringly-typed accessibility identifiers, you can use string constants (NSString * const kIdentifier = @"blah"). It runs by bridging UIAutomation and Objective-C, so its more reliable than KIF, which has to use private API to simulate touches. This doesn't work correctly for gesture recognizers and is very fragile.