Hi Liz,
Elizabeth Keogh wrote:
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.
Having "Story: title" would not be forcing others to adhere to template,
unless e.g. they wanted to use the GivenScenarios/GivenStory directive.
I saw it as required say to have something along the lines:
GivenScenarios path/to/dependent/scenario
Story: This story depends on path/to/dependent/scenario
Scenario: Scenario 1
Scenario: Scenario 2
....
And we can easily adopt the extend-and-deprecate approach for backward
compat.
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.
But ATM, the "scenario" is actually a collection of independent
scenarios (albeit executed in the given order). To me it's more akin to
a story, which is reflected in the Java model too. But it's semantics
more than anything else.
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.
Not quite sure you mean here ...
Are you saying you prefer the ordering of scenarios to the
GivenScenarios approach?
BTW, the natural ordering is already supported. If you use, e.g.
10_my_first_scenario
11_slight_variation_on_10
20_my_second_scenario
30_my_third_scenario
These are executed in both IDE and CLI in the natural order.
I think the GivenScenarios feature addresses a different concern, i.e.
the ability to have each scenario or story to specify its own
pre-requirements in the form of another scenario or story.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
