[
http://jira.codehaus.org/browse/JBEHAVE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-246:
---------------------------------
Fix Version/s: 3.0
> 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
