gmane.comp.java.jmock.devel

[jira] Created: (JMOCK-207) Statically type-safe way of defining expectations for all mock objects of a given type

Nat Pryce (JIRA — 2008-11-22T09:51:41

Statically type-safe way of defining expectations for all mock objects of a given type -------------------------------------------------------------------------------------- Key: JMOCK-207 URL: http://jira.codehaus.org/browse/JMOCK-207 Project: jMock Issue Type: New Feature Components: Library Affects Versions: 2.5.1 Reporter: Nat Pryce Priority: Minor From http://starobjects.blogspot.com/2008/11/jmock-actions-api.html "It would be nice is if the: "allowing(any(Injectable.class)) returned an reference of type Injectable. As it is, the use of method("injectInto") is a little fragile if I were to refactor the name." That exact syntax would not be possible, but we could do: allowing(Foo.class).bar(); That is, pass a class to mean "all instances of this class". It will return an imposteriser to capture the method call.

[jira] Created: (JMOCK-206) Lost test Exception in org.jmock.core.VerifyingTestCase.runBare()

Frédéric Rodrigo (JIRA — 2008-11-07T10:11:14

Lost test Exception in org.jmock.core.VerifyingTestCase.runBare() ----------------------------------------------------------------- Key: JMOCK-206 URL: http://jira.codehaus.org/browse/JMOCK-206 Project: jMock Issue Type: Bug Components: Library Affects Versions: 1.2.0 Environment: Java 1.4 JUnit 3.8.2 Reporter: Frédéric Rodrigo In org.jmock.core.VerifyingTestCase /* This is virtually a copy/paste of the same invokedMethod in the TestCase class to allow * overriding of runTest in the normal manner. * * < at >see junit.framework.TestCase#runBare() */ public void runBare() throws Throwable { setUp(); try { runTest(); verify(); } finally { tearDown(); } } Exception appen in text was lost on try (no catch no throw). In super method junit.framework.TestCase.runBare() there is : /** * Runs the bare test sequence.

[jira] Closed: (JMOCK-204) Documentation does not use the oneOf method

Nat Pryce (JIRA — 2008-09-16T20:59:48

[ http://jira.codehaus.org/browse/JMOCK-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce closed JMOCK-204. --------------------------- Resolution: Fixed

[jira] Updated: (JMOCK-203) CardinalityClause does not include new oneOf method

Nat Pryce (JIRA — 2008-09-15T20:36:48

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

[jira] Created: (JMOCK-205) Deprecate the 'one' method in favour of 'oneOf'

Nat Pryce (JIRA — 2008-09-15T20:34:48

Deprecate the 'one' method in favour of 'oneOf' ----------------------------------------------- Key: JMOCK-205 URL: http://jira.codehaus.org/browse/JMOCK-205 Project: jMock Issue Type: New Feature Components: Library Reporter: Nat Pryce Priority: Trivial

[jira] Updated: (JMOCK-203) CardinalityClause does not include new oneOf method

Nat Pryce (JIRA — 2008-09-15T20:34:48

[ http://jira.codehaus.org/browse/JMOCK-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-203: ---------------------------- Description: The CardinalityClause interface should have the 'oneOf' method since the 'one' method is expected to be deprecated according to the documentation in Expectations. These methods should also be annotated as deprecated. was: The CardinalityClause interface should have the 'oneOf' method since the 'one' method is expected to be deprecated according to the documentation in Expectations. These methods should also be annotated as deprecated. The documentation should also be changed to reflect this change in API. I noticed 'one' is referenced in the sections 'Getting Started', 'Cookbook', and 'Cheat Sheet'. Component/s: (was: Documentation) Moved documentation issues into their own Jira issue

[jira] Resolved: (JMOCK-203) CardinalityClause does not include new oneOf method

Nat Pryce (JIRA — 2008-09-15T20:34:48

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

[jira] Updated: (JMOCK-204) Documentation does not use the oneOf method

Nat Pryce (JIRA — 2008-09-15T20:32:48

[ http://jira.codehaus.org/browse/JMOCK-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-204: ---------------------------- Description: The documentation should also be changed to reflect that "oneOf" is preferred to "one". I noticed 'one' is referenced in the sections 'Getting Started', 'Cookbook', and 'Cheat Sheet'. (was: The CardinalityClause interface should have the 'oneOf' method since the 'one' method is expected to be deprecated according to the documentation in Expectations. These methods should also be annotated as deprecated. The documentation should also be changed to reflect this change in API. I noticed 'one' is referenced in the sections 'Getting Started', 'Cookbook', and 'Cheat Sheet'.) Affects Version/s: (was: 2.5.1) (was: 2.5.0) Chore (ASAP) Fix Version/s: Chore (ASAP) Component/s: (was: Library)

[jira] Created: (JMOCK-204) Documentation does not use the oneOf method

Nat Pryce (JIRA — 2008-09-15T20:30:48

Documentation does not use the oneOf method ------------------------------------------- Key: JMOCK-204 URL: http://jira.codehaus.org/browse/JMOCK-204 Project: jMock Issue Type: Bug Components: Documentation, Library Affects Versions: 2.5.0, 2.5.1 Reporter: Justin Wesley Priority: Minor The CardinalityClause interface should have the 'oneOf' method since the 'one' method is expected to be deprecated according to the documentation in Expectations. These methods should also be annotated as deprecated. The documentation should also be changed to reflect this change in API. I noticed 'one' is referenced in the sections 'Getting Started', 'Cookbook', and 'Cheat Sheet'.

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

Nat Pryce (JIRA — 2008-09-15T20:28:48

[ http://jira.codehaus.org/browse/JMOCK-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nat Pryce updated JMOCK-202: ---------------------------- Component/s: Library

[jira] Commented: (JMOCK-203) CardinalityClause does not include new oneOf method

Nat Pryce (JIRA — 2008-09-15T18:28:48

[ http://jira.codehaus.org/browse/JMOCK-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148011#action_148011 ] Nat Pryce commented on JMOCK-203: --------------------------------- Good point! The one method is not deprecated yet, but will be in a future release.

[jira] Created: (JMOCK-203) CardinalityClause does not include new oneOf method

Justin Wesley (JIRA — 2008-09-15T16:24:48

CardinalityClause does not include new oneOf method --------------------------------------------------- Key: JMOCK-203 URL: http://jira.codehaus.org/browse/JMOCK-203 Project: jMock Issue Type: Bug Components: Documentation, Library Affects Versions: 2.5.1, 2.5.0 Reporter: Justin Wesley Priority: Minor The CardinalityClause interface should have the 'oneOf' method since the 'one' method is expected to be deprecated according to the documentation in Expectations. These methods should also be annotated as deprecated. The documentation should also be changed to reflect this change in API. I noticed 'one' is referenced in the sections 'Getting Started', 'Cookbook', and 'Cheat Sheet'.

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

Corporate Gadfly (JIRA — 2008-09-08T15:08:48

[ http://jira.codehaus.org/browse/JMOCK-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Corporate Gadfly updated JMOCK-201: ----------------------------------- Attachment: JMOCK-201.patch Patch against trunk allowing {{ClassImposteriser}} to be extended.

[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

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 wa

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.