Hi Egil (and Mauro),

Blurb means "a brief summary or description of a work". It's not a
data type as much as a word that I felt described exactly what was
there; a brief summary. It might be in narrative form; it might be a
comment about the scenario.

"Narrative" might be better. However, I don't have "Story: <title>" in
my scenarios; it really is just Blurb for me. If you add a title,
you'll be forcing others to adhere to that template; they may not want
to, especially if their scenario files really are single scenario
files. Perhaps you could find a way to convert the Blurb to your Story
using a converter of some sort?

I'd also prefer generally that we didn't rename existing classes until
3.0 - it tends to break things! Other people may have implemented
their own reporters too.

Re GivenScenario vs. GivenStory - A scenario is a series of steps
which leave you in a clearly defined state. A story has a collection
of independent scenarios - so running them to leave you in a defined
state makes no sense to me.

I can understand wanting priority. I can also understand wanting to
reuse scenarios. The two things are very different, though! If you're
using priority to ensure that a scenario sets up context for another
scenario, that Given will be magically performed, and hidden from
anyone who tries to replicate that scenario manually by reading your
scenario text.

As soon as you do that - use magic in your scenario files - you're
making it impossible for the business to follow them, and you might as
well be writing the scenarios directly in code.

I'm really glad you're experimenting with the flexibility of JBehave.
It makes me happy to see that it does most of the things users want it
to, or can be adapted! Please let us know how the HTML reporting goes,
and remember those of us out there who may be doing things a bit
differently to you. :)

Cheers,
Liz.

-- 
Elizabeth Keogh
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://jbehave.org
http://lizkeogh.com

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

    http://xircles.codehaus.org/manage_email


Reply via email to