[ 
http://jira.codehaus.org/browse/JBEHAVE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mauro Talevi reopened JBEHAVE-472:
----------------------------------


The refactor has broken the failure UUID correlation between stories 
(JBEHAVE-490).

Added FailureCorrelationStories in trader example to reproduce behaviour. 



> Improve state management of StoryRunner
> ---------------------------------------
>
>                 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 
> behaviours when there are failure in the @Before steps but not in the normal 
> steps.  Examples of such a behaviour are the trader 
> failing_before_after.story and failing_before_stories.story.
> A better and more intuitive state management should be in place, keeping 
> state in the run context.  The state should be reset by default before each 
> scenario (to ensure backward compat) but will be shared between the 
> @Before/@After steps and the normal steps.  
> We should also have the option to not reset it before each scenario to allow 
> for failures in the @BeforeStory/Stories steps to propagate to the scenario 
> steps in the same run context.
> Once a failing state in a given run context, the steps that follow will not 
> be performed, as customary with normal 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


Reply via email to