Uploaded image for project: 'XWiki Commons'
  1. XWiki Commons
  2. XCOMMONS-312

Upgrade to JMock 2.6.0 RC2

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • 4.3.1
    • 4.3
    • None
    • N/A
    • N/A

    Description

      We need JMock 2.6.0 and the final is not available but we should still upgrade because ATM we cannot have several @RunWith and JMock is using one to verify if expectations have been met at end of tests. And we also need @RunWith for our custom suites...

      JMock 2.6 fixes this with http://svn.codehaus.org/jmock/trunk/jmock2/src/org/jmock/integration/junit4/JUnitRuleMockery.java

      And a few other things like:

      • a new auto-mocking functionality that reduces boilerplate code
      • support for testing multitheaded code
      • a Mockery that works with JUnit's rules mechanism (that's JUnitRuleMockery)
      • better failure diagnostics.

      See:

      The only downside of JMock 2.6 is a behavior change for matching null which can be considered a regression, see http://jira.codehaus.org/browse/JMOCK-261

      However the workaround described in the issue is pretty simple and I think acceptable for now.

      Attachments

        Issue Links

          Activity

            People

              vmassol Vincent Massol
              vmassol Vincent Massol
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: