Split Kiwi into Kiwi-Core, Kiwi-iOS and Kiwi-Cocoa about kiwi

[allending]

Think this is a pretty good idea. What is there really does not depend on UIKit at all as it it, and so could be considered the foundation. What specific UIKit functionality are you thinking about? Views have been rather finicky w/ regards to testing in my experience.

[dimsumthinking]

Would you then build cucumber like functionality for each platform?

[lukeredpath]

No plans for Cucumber-style testing. I'd recommend looking at Frank which actually uses Cucumber or KIF if you want a general integration testing solution.

However, I'm open to the idea of building some convenient matcher libraries for UIKit-related specs.

[dimsumthinking]

Thanks Luke.

It just seems to me if you are taking this step then you are essentially entering into the functional testing category. Maybe I'm just not seeing it. The only parts of the GUI I generally test are those exposed as Outlets, Actions, etc. Although with O's and A's moving to the .m file, your approach may be more attractive.

Anyway, I'm just an observer and not actually doing the hard work that you guys are doing. I appreciate your efforts.

[alloy]

I have been collecting and working on some GUI related test helper code over the last year, here’s an Nu example or a MacRuby example. (My spec framework is meant to be used with languages other than Objective-C.) It may or may not be interesting to make this a shared thing.

[lukeredpath]

I certainly agree that view testing is something better covered by functional tests that drive the UI.

What I was thinking of was controllers but I'm not sure, I've not done enough unit testing of controllers to know what would be useful and what wouldn't. I need to give this some thought.

[ma11hew28]

What about UIAutomation? I would also recommend separating out the Core, Mocks & Expectations into separate libraries. Like RSpec: https://www.relishapp.com/rspec/

[allending]

Lets look at this as part of #176.