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
