I’ve enjoyed using and writing about Dr Nic’s Rbiphonetest. It’s been cool being able to at least do the testing point of iPhone development in Ruby, which is far more succinct, DRY, and expressive than Objective-C. It’s also handy to be able to take advantage of Ruby’s mature testing frameworks.

I’ve even been able to test the iPhone’s UI widget interactions, which Rbiphonetest is not supposed to do: it needed a hack, but it was a clever hack – and that’s the problem. Rbiphontest is a clever experiment, but it seems to have run its course. Anywhere off the standard path (UI, Catagories, creating one model in another) is strewn with traps and difficulties. Even Dr Nic seems to be discouraging its use.

So expect more blog entries about Rbiphonetest. What I will be writing are some tutorials on doing iPhone TDD using the Google toolbox for Mac. I’ve got something like autotest running with it already. Stay tuned.