To be clear, broadly speaking, I would classify TDD for unit-level testing and BDD for integration-level testing (although as I argued before, once can use BDD concepts in TDD as well ... but let's leave that distinction aside). BDD has more to do with the means of communication and the scope of the system under test that is significant to the stakeholders. Plain text is far more meaningful to most stakeholders than any form of code and a black-box integration test is more interesting to the end user than the interaction of the a class with its dependencies (usually mocked).
I would say that TDD speaks more to the developers and BDD more to the non-technical stakeholders. But far from seeing these in competition, they actually complement each other. In the examples, we focus on the BDD aspect, not the TDD which is very well documented elsewhere. Cheers On 25/08/2010 15:05, [email protected] wrote: > Hi, > > So are you saying the scenarios which match up to business requirements > could involve many classes then? > > I am confused coming from a TDD methodology where the tests being written > drive the development of the class behaviour. So the tests actually become > unit tests. > > Surely if these scenarios are being written correctly seperate tests will > not be required? > > There does not seem to be enough explanation for the reasoning behind > these examples. > > Chris > >> Hi Chris, >> >> the *Behaviour classes provide unit-level testing behaviours, while the >> stories/scenarios provide integration-level testing behaviours. >> >> If you want, the unit-level testing does not use anything specific to >> JBehave (it relies on JUnit and Hamcrest), but it does show that you can >> use BDD concepts at unit-level testing. The "behaviour" here is >> intended as a description and verification of the functionality as >> demostrable via a test. >> >> Cheers > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
