Hi Andy,

The short answer is "Stories are not associated with the behaviour classes".

The full answer is that they are on two different levels.

Behaviour classes are written by developers through BDD practices.
They are the way that developers can make sure that they are writing
high quality code yet not spending too much time on up front design.
You can check out any TDD article for the full description.  That is
why it is in Java, because that is the language developers are most
comfortable with.

The stories are used for the customers to write the acceptance
criteria for the stories that development team has committed to
implement for the current iteration.  Developer will write classes
that will support running the story, but the stories themselves will
be written by customer (or anyone with the authority to say "this
story is done").  That is why they are in plain text because we cannot
expect them understand Java.  This kind of testing is called
acceptance tests, here is another favor of it (http://fit.c2.com/)

Hope this helps

Cheers
--
Shane
http://www.shaneduan.com

On 4/5/07, Andy Zimmerman <[EMAIL PROTECTED]> wrote:
I've been very excited watching the progress you've all made with jBehave
recently.  It looks like I'm finally going to get the opportunity to write
code again, and I'm planning on using BDD (as I understand it today - I'm
sure I'll learn more ;-) ).  However, I'm having one small problem with
jBehave:  I don't grok how the stories and behaviours mesh.

I understand (at least at a basic level) how to use behaviours as I would
have used jUnit tests previously.  I understand that there is a two way path
between text documentation and code via the Stories framework.  What I don't
get is how the (apparently empty) Stories connect to the Behaviours.  What
am I missing?  I feel like it's something super obvious, but I'm just not
getting it (even after looking over the Hellbound example code).

It could be due to me trying to stuff my brain with everything that's
happened in my favorite Open Source framework stack since I last coded, but
I'd appreciate any quick insight or direction you can offer.

Thanks,
Andy Zimmerman


---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to