[ 
http://jira.codehaus.org/browse/JBEHAVE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200441#action_200441
 ] 

Cristiano Gavião commented on JBEHAVE-204:
------------------------------------------

As a workaround to handle failure on the embedded scenario, I've created my own 
class that implements ScenarioReporter: 
{code}public class StepFailureScenarioReporterDecorator2 implements 
ScenarioReporter
        
public void afterStory(boolean embeddedStory) {
                delegate.afterStory(embeddedStory);
                if (embeddedStory == false)
                        if (failure != null) {
                                throw failure;
                        }
        }
{code}

As well I configure my scenarios to use:

{code}
        @Override
        public ErrorStrategy forHandlingErrors() {
                return ErrorStrategy.SILENT;
        }
        @Override
        public PendingErrorStrategy forPendingSteps() {
                return PendingErrorStrategy.PASSING;
        }
{code}


> Scenario runner should report before and after story only once when running 
> given scenarios
> -------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-204
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-204
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>            Priority: Minor
>             Fix For: 2.4
>
>
> When running a scenario with given scenarios, i.e. when running scenarios 
> embedded in another scenario, the scenario runner should only report event 
> beforeStory/afterStory once.   

-- 
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