[jira] Created: (JMOCK-216) Having more one() expectations than actually called doesn't fails

Having more one() expectations than actually called doesn't fails
-----------------------------------------------------------------

                 Key: JMOCK-216
                 URL: http://jira.codehaus.org/browse/JMOCK-216
             Project: jMock
          Issue Type: Bug
          Components: Library
    Affects Versions: 2.5.1
            Reporter: Mike Andrzejewski
         Attachments: JMockBugTest.java

Please find attached an illustration of this bad behaviour.

3 tests are defined. Only one should pass (the second), but the third erroneously passes.


--
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

    [ http://jira.codehaus.org/browse/JMOCK-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168885#action_168885 ]

Steve Freeman commented on JMOCK-216:
-------------------------------------

you appear to be missing the

@RunWith(JMock.class)

annotation on the class. It's there to catch set expectations that have not been called.

> Having more one() expectations than actually called doesn't fails
> -----------------------------------------------------------------
>
>                 Key: JMOCK-216
>                 URL: http://jira.codehaus.org/browse/JMOCK-216
>             Project: jMock
>          Issue Type: Bug
>          Components: Library
>    Affects Versions: 2.5.1
>            Reporter: Mike Andrzejewski
>         Attachments: JMockBugTest.java
>
>
> Please find attached an illustration of this bad behaviour.
> 3 tests are defined. Only one should pass (the second), but the third erroneously passes.

--
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

     [ http://jira.codehaus.org/browse/JMOCK-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nat Pryce closed JMOCK-216.
---------------------------

      Assignee: Nat Pryce
    Resolution: Not A Bug

You must either annotate the class with @RunWith(JMock.class) or explicitly call assertIsSatisfied() on the Mockery.

> Having more one() expectations than actually called doesn't fails
> -----------------------------------------------------------------
>
>                 Key: JMOCK-216
>                 URL: http://jira.codehaus.org/browse/JMOCK-216
>             Project: jMock
>          Issue Type: Bug
>          Components: Library
>    Affects Versions: 2.5.1
>            Reporter: Mike Andrzejewski
>            Assignee: Nat Pryce
>         Attachments: JMockBugTest.java
>
>
> Please find attached an illustration of this bad behaviour.
> 3 tests are defined. Only one should pass (the second), but the third erroneously passes.

--
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