[
http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160633#action_160633
]
Mauro Talevi commented on JBEHAVE-126:
--------------------------------------
I agree that story should be a separate model concept. The issue here is that
we started with the Scenario concept and then added the ability to run multiple
scenarios, which in my mind constitutes a story. So I would only run a story
(ie a set of scenarios) to set up a context for another story - that's why I
was thinking of calling it GivenStory. I think this could be retrofitted in
2.x codebase, possibly. Else we could branch off a 3.x and revisit the whole
model to be more story-aware.
The alternative of keeping the GivenScenario as a context set up for each
scenario is possible, but complicates the parsing IMO in case you had multiple
GivenScenario in a single file. We need to evaluate which of the two use cases
is more used. I'm thinking that most likely users would need a single setup
call for all the scenarios in their file.
> 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
