mockit.integration.junit4.package-info Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of jmockit Show documentation
Show all versions of jmockit Show documentation
JMockit is a Java toolkit for automated developer testing.
It contains mocking/faking APIs and a code coverage tool, supporting both JUnit and TestNG.
The mocking APIs allow all kinds of Java code, without testability restrictions, to be tested
in isolation from selected dependencies.
/*
* Copyright (c) 2006 Rogério Liesenfeld
* This file is subject to the terms of the MIT license (see LICENSE.txt).
*/
/**
* Provides integration with JUnit 4.x test runners, for version 4.5 or newer.
* Contains the {@link mockit.integration.junit4.JMockit} custom test runner (which is not an actual test runner, but
* just a way to ensure that JMockit gets properly initialized - a better way is to simply put {@code jmockit.jar}
* before {@code junit.jar} in the test runtime classpath).
*
* This integration provides the following benefits to test code:
*
* -
* Instance fields annotated with {@code @Tested}, {@code @Injectable}, {@code @Mocked}, or {@code @Capturing}
* are properly initialized.
*
* -
* Test methods accept mock parameters (annotated with {@code @Injectable}, {@code @Mocked}, or
* {@code @Capturing}), whose values are mocked instances automatically created by JMockit and passed by the test
* runner when the test method is executed.
*
* -
* Expected invocations specified through the Expectations API are automatically verified before the execution of
* a test is completed.
*
* -
* Mock-up classes applied with the Mockups API from inside a method annotated as a {@code @Test} or a
* {@code @Before} method are discarded right after the execution of the test method or the whole test,
* respectively.
* Similarly, mock-ups applied from a {@code @BeforeClass} method are discarded after all tests in a test class
* have executed.
*
*
*/
package mockit.integration.junit4;