gmane.comp.java.jmock.devel

[jira] Created: (JMOCK-202) Unsatisfied expectations are not correctly captured with JUnit4's < at >Test(expected=AssertionError.class) in JMock 2.5.0-RC1+

Steven Cummings (JIRA — 2008-09-02T18:22:48

Unsatisfied expectations are not correctly captured with JUnit4's < at >Test(expected=AssertionError.class) in JMock 2.5.0-RC1+ -------------------------------------------------------------------------------------------------------------------------- Key: JMOCK-202 URL: http://jira.codehaus.org/browse/JMOCK-202 Project: jMock Issue Type: Bug Affects Versions: 2.5.1, 2.5.0, 2.5.0-RC1 Environment: JMock 2.5.0-RC1+ JUnit 4.4 Java 1.5.0_16 Ubuntu Linux 8.0.4 kernel 2.6.24-19-generic Reporter: Steven Cummings Attachments: JMockBugTest.java This was working up through version 2.4.0. I am testing some custom matchers with JMock by writing expectations that I expect to be unsatisfied when the test completes, and therefore I expect an AssertionError. From JMock 2.5.0-RC1 and on, < at >RunWith(JMock.class) causes < at >Test(expected=AssertionError.class) to fail to capture the resulting exception. When I say JMock 2.5.0-RC1+, I mean I could reproduce the problem with versions 2.5.0-RC1, 2.5.0, 2.5.0.1, and 2.5.1.

a() and an()

2008-08-29T20:27:52

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

[jira] Created: (JMOCK-201) Allow ClassImposteriser to be extended

Corporate Gadfly (JIRA — 2008-08-29T16:32:48

Allow ClassImposteriser to be extended -------------------------------------- Key: JMOCK-201 URL: http://jira.codehaus.org/browse/JMOCK-201 Project: jMock Issue Type: Improvement Components: Library Affects Versions: 2.5.1 Reporter: Corporate Gadfly I had a need to imposterise concrete classes (from 3rd-party jars) with final toString() method. For background, please see discussion at: http://www.nabble.com/Re%3A-mocking-concrete-classes-with-final-toString-method-p18509146.html In that thread, Nat had advised one of the options as being "write your own Imposteriser". So, for my needs I ended up writing ClassImposteriserAllowingFinalToString. It would be great if ClassImposteriser could be made easier to extend. As it is, it has a lot of private methods and properties and I pretty much had to rewrite my own imposteriser from scratch (essentially duplicating the private pieces of ClassImposteriser). If ClassImposteriser was extension friendly, I would probably need to do minimal work by writing my own imposterise() and canImposterise() methods. This way I would also be safeguarded against future bug-fixes that may happen in ClassImposteriser. Cheers and thanks in advance.

2.5.1 Released

Nat Pryce — 2008-08-24T10:20:55

We've just released jMock 2.5.1, a bug-fix release that improves error messages. The changelog is at: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10336&styleName=Html&version=14527 --Nat --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

[jira] Resolved: (JMOCK-200) JMock does not report actual invocations when the mockery is not satisfied

Nat Pryce (JIRA — 2008-08-24T10:00:27

[ http://jira.codehaus.org/browse/JMOCK-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce resolved JMOCK-200. ----------------------------- Resolution: Fixed Fix committed to 2.5.1 branch and merged to trunk.

[jira] Updated: (JMOCK-200) JMock does not report actual invocations when the mockery is not satisfied

Nat Pryce (JIRA — 2008-08-24T10:00:27

[ http://jira.codehaus.org/browse/JMOCK-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-200: ---------------------------- Assignee: Nat Pryce Description: JMock does not report actual invocations when the mockery is not satisfied, only when an unexpected invocation is received Fix Version/s: 2.5.1

[jira] Created: (JMOCK-200) JMock does not report actual invocations when the mockery is not satisfied

Nat Pryce (JIRA — 2008-08-24T00:02:26

JMock does not report actual invocations when the mockery is not satisfied -------------------------------------------------------------------------- Key: JMOCK-200 URL: http://jira.codehaus.org/browse/JMOCK-200 Project: jMock Issue Type: Bug Components: Library Affects Versions: 2.5.0 Reporter: Nat Pryce Priority: Minor

[jira] Resolved: (JMOCK-199) Upgrade to CGLIB 2.2

Nat Pryce (JIRA — 2008-08-14T12:25:26

[ http://jira.codehaus.org/browse/JMOCK-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce resolved JMOCK-199. ----------------------------- Resolution: Fixed Implemented in SVN.

[jira] Created: (JMOCK-199) Upgrade to CGLIB 2.2

Nat Pryce (JIRA — 2008-08-13T22:23:27

Upgrade to CGLIB 2.2 -------------------- Key: JMOCK-199 URL: http://jira.codehaus.org/browse/JMOCK-199 Project: jMock Issue Type: Improvement Components: Library Affects Versions: 2.5.0 Reporter: Nat Pryce Fix For: 2.6.0

[jira] Updated: (JMOCK-172) Make it easy to define a block of expectations that only occur in a given state

Nat Pryce (JIRA — 2008-08-13T16:22:27

[ http://jira.codehaus.org/browse/JMOCK-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-172: ---------------------------- Priority: Minor (was: Major)

[jira] Issue Comment Edited: (JMOCK-185) new will() methods for terse referring to parameters.

Nat Pryce (JIRA — 2008-08-09T08:48:26

[ http://jira.codehaus.org/browse/JMOCK-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128889#action_128889 ] npryce edited comment on JMOCK-185 at 8/9/08 3:47 AM: --------------------------------------------------------- This can also be achieved with the scripting extension which is in version 2.5.0. See issue JMOCK-174. was (Author: npryce): This can also be achieved with the scripting extension which is currently in SVN HEAD. See issue JMOCK-174.

[jira] Resolved: (JMOCK-192) Support the new test runner architecture in JUnit 4.5

Nat Pryce (JIRA — 2008-08-08T23:11:26

[ http://jira.codehaus.org/browse/JMOCK-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce resolved JMOCK-192. ----------------------------- Resolution: Fixed Committed to trunk

[jira] Updated: (JMOCK-198) Allow assert of State-Machine

Nat Pryce (JIRA — 2008-08-08T22:57:27

[ http://jira.codehaus.org/browse/JMOCK-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-198: ---------------------------- Issue Type: New Feature (was: Improvement)

[jira] Updated: (JMOCK-167) Don't report "returns a default value" for void methods

Nat Pryce (JIRA — 2008-08-08T22:55:27

[ http://jira.codehaus.org/browse/JMOCK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-167: ---------------------------- Fix Version/s: (was: 2.7.0) 2.6.0

[jira] Commented: (JMOCK-197) Mocking a static nested class causes a net.sf.cglib.core.CodeGenerationException to be thrown.

Nat Pryce (JIRA — 2008-08-08T22:53:26

[ http://jira.codehaus.org/browse/JMOCK-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144554#action_144554 ] Nat Pryce commented on JMOCK-197: --------------------------------- Great! Thanks.

[jira] Resolved: (JMOCK-198) Allow assert of State-Machine

Nat Pryce (JIRA — 2008-08-08T22:51:27

[ http://jira.codehaus.org/browse/JMOCK-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce resolved JMOCK-198. ----------------------------- Resolution: Fixed Fix Version/s: 2.6.0 Implementation committed to SVN.

[jira] Commented: (JMOCK-198) Allow assert of State-Machine

Nat Pryce (JIRA — 2008-08-08T22:51:27

[ http://jira.codehaus.org/browse/JMOCK-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144552#action_144552 ] Nat Pryce commented on JMOCK-198: --------------------------------- Unfortunately that patch is still not acceptable. * Matchers must be stateless (e.g. immutable). Your matcher stores the matched parameter in an instance variable. * The patch contains commented out code * The patch mixes formatting changes and new functionality. I've committed an implementation to SVN head.

[jira] Resolved: (JMOCK-195) mail archives are out of date

Nat Pryce (JIRA — 2008-08-08T18:47:26

[ http://jira.codehaus.org/browse/JMOCK-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce resolved JMOCK-195. ----------------------------- Resolution: Fixed The developers list is being archived again.

[jira] Commented: (JMOCK-197) Mocking a static nested class causes a net.sf.cglib.core.CodeGenerationException to be thrown.

Ryan C. Payne (JIRA — 2008-08-07T14:51:26

[ http://jira.codehaus.org/browse/JMOCK-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144403#action_144403 ] Ryan C. Payne commented on JMOCK-197: ------------------------------------- Sure thing. I will whip that up this afternoon and attach it to the JIRA.

[jira] Commented: (JMOCK-197) Mocking a static nested class causes a net.sf.cglib.core.CodeGenerationException to be thrown.

Nat Pryce (JIRA — 2008-08-07T14:49:27

[ http://jira.codehaus.org/browse/JMOCK-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144402#action_144402 ] Nat Pryce commented on JMOCK-197: --------------------------------- If you could give us a small, self-contained JUnit test that demonstrates the problem, that would be a great help in tracking this down.

[jira] Updated: (JMOCK-198) Allow assert of State-Machine

Marcos Sanchez (JIRA — 2008-08-06T09:24:26

[ http://jira.codehaus.org/browse/JMOCK-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcos Sanchez updated JMOCK-198: --------------------------------- Attachment: (was: StateMachineMatchers2.txt)