Hacker News new | ask | show | jobs
by tvon 4827 days ago
Well, I don't really agree, but I will say that the iOS testing world has a lot of catch-up to do. Ruby developers (as an example) have much, much, much better testing tools. There is no doubt about that. The hoops you have to jump through to create acceptance tests are quite annoying, especially when you can't even test UIAlertViews, or basic things like Airplane Mode...
2 comments

I don't think that's a fair comparison. Testing GUI code has always been a lot trickier than testing backend code, and iOS apps tend to be GUI-oriented while Ruby projects tend to be backend-oriented.

That's not to say that the iOS testing tools are great, but I've never had a particularly pleasant time testing GUI code on any platform.

True, Ruby doesn't usually get used for GUIs. But take a look at the Javascript and browser testing tools that are available. Is there anything like Sauce Labs for iOS?
Why not jump into RubyMotion and use these testing tools?

And Apple's WWDC session about acceptance tests using Instruments UI Automation specifically handles UIAlertView.

I think the problem is that iOS apps are getting dumber and dumber while their UI bling gets more complicated/asynchronous. The value of tests is too low for The One Widely Accepted Testing Framework to emerge.