BDD for Scribbeo

[kfatehi]

We're in agreement that a very important thing to do with Scribbeo before all else, is to get this sucker well-tested so we can avoid regressions.

This ticket will serve to:

• Guide in selecting the best method(s) of testing, see http://stackoverflow.com/questions/4114083/ios-tests-specs-tdd-bdd-and-integration-acceptance-testing
• Provide a place to write documentation for how to use the test suite once installed in the src

[kfatehi]

Zucchini Framework seems to blend Cucumber & UI Automation! http://www.zucchiniframework.org/

[mixflame]

Zucchini looks good. Agree here. Good testing will see us to success.

[mixflame]

One thing to note. It is better to hit "record" and then test the whole app then to have to write a bunch of tests for already written code. If this exists.

[mixflame]

There's another problem here on top of my last note. Writing tests for already existing code isn't BDD. The reason is that it's Behavior Driven. So yeah it's probably a waste of our time here to try to test like that, unless we can come up with some kind of tool that just records it like Selenium. I may be wrong, though.

[kfatehi]

You're right, and there seems to be some tools in Instruments for recording interaction, and I believe you can check state with a screenshot using Zuchini once that automation has completed... We'll learn more as we spend more time on this but we can definitely both agree that we need to have something that establishes our baseline for Scribbeo to secure us from regression. BDD will be a great tool for adding new functionality and will be indispensable in our iOS dev workflow just as it has been in Ruby.

[kfatehi]

I like Frank. I checked it out, works and looks promising!