JMockit development history

Next release

Release 1.8 (Apr 27, 2014):

Current release

Release 1.7 (Mar 9, 2014):

Previous releases

Release 1.6 (Dec 23, 2013):

Release 1.5 (Oct 20, 2013):

Release 1.4 (Aug 21, 2013):

Release 1.3 (Jun 23, 2013):

Release 1.2 (Apr 21, 2013):

Release 1.1 (Feb 25, 2013):

Release 1.0 (Dec 20, 2012):

Release 0.999.19 (Nov 19, 2012):

Release 0.999.18 (Oct 18, 2012):

Release 0.999.17 (Sep 17, 2012):

Release 0.999.16 (Jul 30, 2012):

Release 0.999.15 (Apr 30, 2012):

Release 0.999.14 (Mar 30, 2012):

Release 0.999.13 (Feb 23, 2012):

Release 0.999.12 (Dec 22, 2011):

Release 0.999.11 (Oct 21, 2011):

From this version on, JMockit artifacts are deployed to the Maven Central repository, under a different "<groupId>" of "com.googlecode.jmockit". Therefore, Maven users should change JMockit dependencies in their pom.xml files accordingly.

Release 0.999.10 (Jun 16, 2011):

Release 0.999.9 (May 17, 2011):

Release 0.999.8 (March 11, 2011):

Release 0.999.7 (February 13, 2011):

Release 0.999.6 (January 30, 2011):

Release 0.999.5 (December 28, 2010):

From this version on, the Java.net Maven 2 repository is no longer used. Project artifacts are now deployed here. Therefore, Maven users should configure the new repository in their pom.xml files.

Release 0.999.4 (December 5, 2010):

Release 0.999.3 (October 3, 2010):

Release 0.999.2 (August 22, 2010):

Release 0.999.1 (July 25, 2010):

Release 0.999 (July 15, 2010):

Release 0.998 (April 21, 2010):

Release 0.997 (March 3, 2010):

Release 0.996 (January 24, 2010):

Release 0.995 (December 20, 2009):

Release 0.994 (December 6, 2009):

Release 0.993 (November 15, 2009):

Release 0.992 (November 8, 2009):

Release 0.991 (October 25, 2009):

Release 0.990 (October 4/6, 2009):

Release 0.989 (September 20, 2009):

Release 0.988 (September 6, 2009):

Release 0.987 (August 17, 2009):

Release 0.986 (July 27, 2009):

Release 0.985 (July 12, 2009):

Release 0.984 (July 5, 2009):

Release 0.983 (June 29/30, 2009):

Release 0.982 (June 19, 2009):

Release 0.981 (June 14, 2009):

Migrating from a previous release

The following changes need to be made to existing JUnit test suites, when migrating from JMockit release 0.97 (or older) to newer releases.

  1. First of all, recompile all test sources with the new jmockit.jar in the classpath.
  2. Any test classes that extended junit.framework.TestCase now need to extend mockit.integration.junit3.JMockitTestCase, unless the test suite is always run with "-javaagent:jmockit.jar". Alternatively, the test class can be converted to JUnit 4, with the addition of @RunWith(JMockit.class) to the class and of @Test to its test methods.
  3. In any test class which itself extends mockit.Expectations, if there is any initialization of instance fields outside of a @Before/setUp method, then a JUnit fixture setup method will have to be created to perform the initialization. This is necessary because now any mock fields of the test class will only be assigned after the test class instance is created (but before any setup or test methods are executed).
  4. If an Expectations subclass (which can be a test class, an anonymous inner class inside a test method, and so on) declares two or more mock fields of the same type or with a common base type, then these fields must mock exactly the same set of methods and constructors belonging to the common class types. By default, all methods and constructors are mocked, so this issue can only happen when (static) partial mocking is used, through the methods or value attribute of the MockField/Mocked annotation. So, if that's the case, simply copy the mock filters specified in one mock field to the others.
  5. JMockit now restores mocked classes automatically both for test-scoped and test class-scoped mocks. Consequently, none of the methods Mockit.tearDownMocks(), Mockit.restoreAllOriginalDefinitions(), or Mockit.restoreOriginalDefinition(...) need to be explicitly called anymore, unless a given test method really needs to restore some mocked class before the test completes its execution. This also means that classes that remained mocked between tests or from one test class to the next in the suite, will not remain mocked as before, but will be restored automatically either between individual tests, or from one test class to the next. Therefore, it will be necessary to set up the mocks again at the appropriate point (for example, in a @Before or @BeforeClass method when using JUnit 4).

It should be easy enough to adapt existing tests according to the incompatibilities listed above. If after making such changes some tests remain broken that weren't before, please let me know.

Release 0.98 (June 7, 2009):

Release 0.97 (May 10, 2009):

Release 0.96 (April 21, 2009):

Release 0.95 (October 19, 2008):

Release 0.94/b/c (January 30/February 14/March 29, 2008):

Release 0.93 (January 14, 2008):

Release 0.92/0.91 (January 4, 2008):

Release 0.90 (November 11, 2007):

Release 0.86 (September 13, 2007):

Release 0.85 (May 20, 2007)

Release 0.84 (March 9, 2007)

Release 0.83 (November 26, 2006)

Release 0.81 (June 2, 2006)