) Testing the happy path is pretty straight forwardQuick and to the point and quite understandable if you ask me, but the thing is that only developers like to read code. UI testing is not exactly a task developers like to do and is usually delegated to people that handle specs and lengthy docs. This is where easyb comes in, I'll let the code speak for itself
As you can see the actual code is exactly the same, but there is a nice separation of preconditions, effects and assertions, and if you enable reporting you get the following output
1 scenario (including 0 pending) executed successfully
Story: easyb fest
scenario User writes a word available in the dictionary
given WordFinder's UI is shown
when user types the word 'pugnacious'
when user clicks on the find button
then the correct answer is displayed (Combative in nature; belligerent.)
then the UI shutdowns itself
Now that is more like it don't you think? The very nature of easyb makes writing scenarios and stories quite simple, as a matter of fact anybody can do it. Once they are written a developer takes the executable spec and writes the code that makes the tests turn green, and everybody is content. I'm so loving easyb...
Keep on Groovying!
