[
http://jira.codehaus.org/browse/JBEHAVE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214659#action_214659
]
Mauro Talevi commented on JBEHAVE-246:
--------------------------------------
A story is made of multiple scenarios, not the other way around. A scenario
may depend on other scenarios as a precondition, hence the GivenScenarios
keyword.
That said, yours is a fair issue being raised as in JBehave 2.x the scenario is
the central element, while upon retrospective placing it at story level might
serve the purpose better. Most like this cannot be done without breaking
backward compat, so we'll address it as part of 3.x.
We still need to ensure that the the ability to execute a single scenario, i.e.
a sequence of steps, without lots of unnecessary scaffolding around it, is
satisfied.
> Improve terminology, the distinction between a story and a scenario
> -------------------------------------------------------------------
>
> Key: JBEHAVE-246
> URL: http://jira.codehaus.org/browse/JBEHAVE-246
> Project: JBehave
> Issue Type: Improvement
> Reporter: James Ravn
> Fix For: 3.0
>
>
> I think it's unfortunate that a scenario file contains several other
> scenarios. This leads to some ambiguities in the system, such as the meaning
> of a {{GivenScenario}}, and also in communication (is a scenario a collection
> or a scenario?).
> It also is somewhat a violation of the literal meaning of scenario - which by
> definition contains other stories or scenes, not scenarios.
> I think while the framework is still relatively young it would be worth
> addressing this design choice. Perhaps a scenario should contain stories, or
> something like that.
> The main concern is removing the ambiguity about what a scenario is.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
