org.powermock.api.easymock.annotation.MockStrict Maven / Gradle / Ivy
package org.powermock.api.easymock.annotation;
import org.powermock.core.classloader.annotations.PowerMockListener;
import java.lang.annotation.*;
/**
* This annotation can be placed on those fields in your test class that should
* be mocked in a strict manner (i.e. the order of method calls are checked).
* This eliminates the need to setup and tear-down mocks manually which
* minimizes repetitive test code and makes the test more readable. In order for
* PowerMock to control the life-cycle of the mocks you must supply the
* {@link PowerMockListener} annotation to the class-level of the test case. For
* example when using the EasyMock API:
*
*
* @PowerMockListener(EasyMockAnnotationEnabler.class)
* public class PersonServiceTest {
*
* @MockStrict
* private PersonDao personDaoMock;
*
* private PersonService classUnderTest;
*
* @Before
* public void setUp() {
* classUnderTest = new PersonService(personDaoMock);
* }
* ...
* }
*
*
*
* Note that you can also create partial mocks by using the annotation. Let's
* say that the PersonService has a method called "getPerson" and another method
* called "savePerson" and these are the only two methods that you'd like to
* mock. Rewriting the previous example to accommodate this will give us the
* following test:
*
*
* @PowerMockListener(EasyMockAnnotationEnabler.class)
* public class PersonServiceTest {
*
* @MockStrict({"getPerson", "savePerson"})
* private PersonDao personDaoMock;
*
* private PersonService classUnderTest;
*
* @Before
* public void setUp() {
* classUnderTest = new PersonService(personDaoMock);
* }
* ...
* }
*
*
*
*/
@Target( { ElementType.FIELD })
@Retention(RetentionPolicy.RUNTIME)
@Documented
@Inherited
public @interface MockStrict {
String[] value() default "";
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy