[
http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153097#action_153097
]
Mauro Talevi commented on JBEHAVE-146:
--------------------------------------
Paul - PASSING and SILENT are implementations of different types (albeit one
extending the other). Similarly, for FAILING and RETHROW.
They address different concerns - the ErrorStrategy and PendingErrorStrategy -
and the fact that the implementation is the same is accidental.
This is expressed by the fact also by their different names.
As for the additional PendingErrorStrategy - could you please provide a test
case (updating the existing ScenarioRunnerBehaviour) or a scenario to show the
use case.
> PendingErrorStrategy choices needs one more.
> --------------------------------------------
>
> Key: JBEHAVE-146
> URL: http://jira.codehaus.org/browse/JBEHAVE-146
> Project: JBehave
> Issue Type: Wish
> Affects Versions: 2.1
> Reporter: Paul Hammant
>
> PASSING and SILENT are identical method bodies
> The same is true of FAILING and RETHROW
> [ moving past that issue ]
> Could y'all make one more strategy ?
> {noformat}
> /**
> * This will continue the scenario as PASSING would, but at the end,
> remember that there was an issue during the run, and throw it again then.
> */
> PendingErrorStrategy FAIL_LATER = new PendingErrorStrategy() {
> public void handleError(Throwable throwable) {
> // ??
> }
> };
> {noformat}
> Note, I've even given you some /** Javadoc */ for this, as
> http://jbehave.org/javadoc/latest/core/org/jbehave/scenario/errors/PendingErrorStrategy.html
> is a little sparse on information ;-)
--
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
