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
There is a newer version: 0.999.4
/*
 * JMockit
 * Copyright (c) 2006-2010 Rogério Liesenfeld
 * All rights reserved.
 *
 * Permission is hereby granted, free of charge, to any person obtaining
 * a copy of this software and associated documentation files (the
 * "Software"), to deal in the Software without restriction, including
 * without limitation the rights to use, copy, modify, merge, publish,
 * distribute, sublicense, and/or sell copies of the Software, and to
 * permit persons to whom the Software is furnished to do so, subject to
 * the following conditions:
 *
 * The above copyright notice and this permission notice shall be
 * included in all copies or substantial portions of the Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
 * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
 * IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
 * CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
 * TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
 * SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 */

/**
 * Provides integration with JUnit 4.x test runners.
 * 
 * Contains special helper classes for users of JUnit 4.5+: the
 * {@link mockit.integration.junit4.JMockit} test runner which is nothing more than the standard
 * JUnit 4.5+ test runner integrated to JMockit, and the
 * {@link mockit.integration.junit4.JMockitTest} convenience base test class.
 * 

 * Also contains the "startup mock" implementation for integration with the JUnit 4.5+ test runner
 * (JUnit 4.4 had a different test runner which was deprecated, and is no longer supported by
 * JMockit).
 * 

 * The integration adds the following benefits to test code:
 * 

 * 
 * Unexpected invocations specified through the Annotations or the Expectations API are
 * automatically verified just before the execution of a test ends (that is, after the test itself
 * executed, but before any {@code @After} methods are executed).
 * 
 * 
 * Any mock classes applied with the Annotations API from inside a test method will be discarded
 * before the execution of the test method ends, so it is not necessary to call
 * {@link mockit.Mockit#tearDownMocks()} at the end of the test, be it from inside the test method
 * itself or from an {@code @After} method.
 * The same is not true for mocks applied in a {@code @Before} method, however: you
 * will need to explicitly tear down those mock classes in an {@code @After} method, so
 * that the mocked real classes are properly restored to their original definitions.
 * 
 * 
 * Any {@linkplain mockit.MockClass mock class} set up for the whole test class (either through
 * a call to {@link mockit.Mockit#setUpMocks} from inside a {@code @BeforeClass} method, or by
 * annotating the test class with {@link mockit.UsingMocksAndStubs}) will only apply to the test
 * methods in this same test class.
 * That is, you should not explicitly tell JMockit to restore the mocked classes in an
 * {@code @AfterClass} method.
 * 
 * 
 */
package mockit.integration.junit4;