[
http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189978#action_189978
]
Mauro Talevi commented on JBEHAVE-126:
--------------------------------------
Thanks for your comments - interesting post.
The use case for GivenScenarios is still quite valid IMO - but it addresses a
different concern from what you describe in your post, i.e. it's not about
calling a scenario from another within the same feature. Rather it's about
using a different story or feature as a pre-condition for a scenario. It's not
meant to be called before each scenario (like background). You could debate
whether it should be called GivenStory or GivenFeature but it does not change
the substance of the matter.
This feature allows scenarios (or features) to have less repetition and be
structured in a more modular and reusable way, without enforcing an order on
the scenarios being run (e.g. by scenario file name). Experience in working
with hundreds of scenarios has shown us how useful this feature can be, and it
has been one of the most highly requested features I received as feedback. It
is particularly useful when running in an IDE.
> GivenScenarios
> --------------
>
> Key: JBEHAVE-126
> URL: http://jira.codehaus.org/browse/JBEHAVE-126
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Elizabeth Keogh
> Assignee: Mauro Talevi
> Fix For: 2.3
>
>
> As someone writing scenarios, I want to be able to use another scenario as a
> Given, so that I don't have to write big long scenarios.
> Not sure how this would work - at the moment we can get around it on the code
> side. I'm guessing we're looking for something like
> Given the glider
> where the_glider is a scenario file.
> (What would we do if the_glider had two scenarios in it? Throw an exception,
> maybe?)
--
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
