Briefly put, in TDD, you write a test first, if the test fails, write only that much code to make it pass and if the test passes, write another test. The goal is to write a new unit test once the previous test has passed. Let the design evolve from this sequence.
Once the code is stable, brush it up with some re-factoring and showcase it (or present it) to the tester for user acceptance tests. If the tester comes up with bugs or with exceptions, go back to the previous step of writing more unit tests to be able to determine what code should be written for the user acceptance to happen!
In UADD, start backwards. Get the UAC and then start your TDD ! Simple !
BDD is just a step further ! :)
http://ravichandranjv.blogspot.in/2012/11/bdd-with-nbehave-starter-example.html
http://ravichandranjv.blogspot.in/2012/11/behavior-driven-development-with-tumbler.html
Happy TDD & UADD !
Once the code is stable, brush it up with some re-factoring and showcase it (or present it) to the tester for user acceptance tests. If the tester comes up with bugs or with exceptions, go back to the previous step of writing more unit tests to be able to determine what code should be written for the user acceptance to happen!
In UADD, start backwards. Get the UAC and then start your TDD ! Simple !
BDD is just a step further ! :)
http://ravichandranjv.blogspot.in/2012/11/bdd-with-nbehave-starter-example.html
http://ravichandranjv.blogspot.in/2012/11/behavior-driven-development-with-tumbler.html
Happy TDD & UADD !
No comments:
Post a Comment