[
http://jira.codehaus.org/browse/JBEHAVE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-472 started by Mauro Talevi.
> StoryRunner should manage state at scenario level
> -------------------------------------------------
>
> Key: JBEHAVE-472
> URL: http://jira.codehaus.org/browse/JBEHAVE-472
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.3
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 3.4
>
>
> We need to improve the state management of the StoryRunner.
> Currently after every set of steps run the state is reset and the scenario
> @Before/@After steps are run separately from the normal steps, causing
> wierd/wrong behaviours when there are failure in the @Before steps but not in
> the normal steps. An example of such a behaviour is the trader
> failing_before_after.story.
> If we use the storyFailure to drive the state it causes other behaviour to
> break. A better and more intuitive state management should be kept at
> scenario level. We should instead hold a reference to a scenarioFailure
> which can be reset before each scenario but will be shared between the
> @Before/@After steps and the normal scenario steps.
--
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
