[
http://jira.codehaus.org/browse/JBEHAVE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-165:
---------------------------------
Attachment: JBEHAVE-165.patch
Simplest patch to satisfy this requirement at Mojo/Task level.
> Enable scenarios to run in fail-batch mode
> ------------------------------------------
>
> Key: JBEHAVE-165
> URL: http://jira.codehaus.org/browse/JBEHAVE-165
> Project: JBehave
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: Mauro Talevi
> Priority: Minor
> Fix For: 2.3
>
> Attachments: JBEHAVE-165.patch
>
>
> Currently, scenario fail in fail-fast mode (unless the ignoreFailure flag is
> enabled).
> A fail-batch mode can often be useful to enable long scenario builds to run
> through and to be have a summary batch failure at the end of the execution.
> An easy way to implement this is at ScenarioRunnerMojo/Task level - but more
> and more there seems to be a more structured abstraction for running
> scenarios, so as to avoid duplication of very similar code. Possibly use
> the Monitor pattern to abstract logging mechanisms of Ant and Maven.
--
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
