[
http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160629#action_160629
]
Elizabeth Keogh commented on JBEHAVE-126:
-----------------------------------------
GivenStory doesn't make any sense to me. I'm starting to think that Story,
being another BDD domain term, should be a completely separate object from
Scenario (and the various types of Scenario). It might have Scenarios as part
of it. To run a GivenScenario, we might want to identify which Scenario in the
Story is being run.
Running all the Scenarios in a story to set up the context for anther Scenario
makes no sense to me. Each Scenario could well leave the application in a
different state, so what context would you set up in the Given? What state
would you have, in which to perform the other steps?
No idea how Story as a separate object would work, but it feels like the right
thing to do. Thoughts? 3.0 maybe?
> 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.2
>
>
> 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
