[
http://jira.codehaus.org/browse/JMOCK-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167258#action_167258 ]
Nat Pryce commented on JMOCK-183:
---------------------------------
The code in JMOCK-59 is addressing a different issue. This issue has nothing to do with multithreading but is required for jMock to report errors correctly if it is made thread-safe (JMOCK-213).
> Exceptions thrown by expectations should be caught and available for rethrowing during verification
> ---------------------------------------------------------------------------------------------------
>
> Key: JMOCK-183
> URL:
http://jira.codehaus.org/browse/JMOCK-183> Project: jMock
> Issue Type: Bug
> Components: Library
> Affects Versions: 2.4.0
> Environment: all
> Reporter: Steve Freeman
> Fix For: 2.7.0
>
>
> At present, Mockery.assertIsSatisfied() flushes any expectations errors that have been thrown during a test but that have not stopped it. Nat and I can't think of a case where there's a good reason to do this. The effect is that if an ExpectationError is thrown but caught and dropped by the code under test, then the test will pass. What we think /should/ happen is that such exceptions should be recorded (which they are) and rethrown if still present during verification.
> This would invalidate CascadedFailuresAcceptanceTests.testSuccessfulVerifyClearsFirstFailure()
--
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
