Miguel Moquillon wrote >> In summary, the intent of BDD is to be "TDD Done Right". > I don't agreed with your assumption: there is a difference > philosophically both in theory and in practice.
In actuality, it is a bit overstated, because one key insight of BDD was to bring /all/ stakeholders into TDD. "In order that... as a... I want..." was intended as a way to have the customer write a spec that would become an executable part of the test framework. But, they're also not as totally independent as you describe. In fact, Dan North, the inventor of BDD has explained it such - that BDD = TDD if your whole team are programmers, but BDD includes: TDD if the stakeholders include non-programmers. ----- Cheers, Sean -- View this message in context: http://forum.world.st/TDD-and-BDD-tp4820612p4821109.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
