[
http://jira.codehaus.org/browse/JBEHAVE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-145.
----------------------------------
Resolution: Fixed
Phil, applied patch with thanks. I've renamed decorator to
StepFailureScenarioReporterDecorator and made StepFailure extend
RuntimeException. I also nullified the failure before each story.
As this is a decorator and does not impact any existing functionality, I think
we can release as is and improve on it in the following release, also looking
at how we can possibly implement via ErrorStrategy.
> Unit-test runners should decorate Exceptions a bit more clearly
> ----------------------------------------------------------------
>
> Key: JBEHAVE-145
> URL: http://jira.codehaus.org/browse/JBEHAVE-145
> Project: JBehave
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Paul Hammant
> Fix For: 2.2
>
> Attachments: step_in_exception.txt
>
>
> Somewhere deep down in the runScenario logic, you could benefit from a
> try/catch(Throwable)/wrap-rethrow
> The wrapping exception could add textual information on the step that is
> failing. Catch throwable because you're not just catching AssertionErrors,
> you're catching Selenium timeouts.
--
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
