PowerMock 1.6 isn’t compatible with Mockito 2.7 (take a look at https://github.com/powermock/powermock/wiki/Mockito#supported-versions) You should use PowerMock 1.7.0RC2 (or 1.7.0RC3 if 1.7.0RC2 doesn’t work), and also use powermock-api-mockito2 instead of powermock-api-mockito.
Answer is as below. After consulting here http://code.google.com/p/powermock/issues/detail?id=278 , in fact Adder.add(12) above is part of setting up mock static method. It means when invoking Adder.add() with argument 12, IOException will be thrown. It is hard to understand, right? 🙂 So it should be written as below. PowerMockito.mockStatic(Adder.class); PowerMockito.doThrow(new IOException()).when(Adder.class); Adder.add(anyInt()); EDIT: Link is dead, … Read more
Make sure you add @RunWith(PowerMockRunner.class) to the top of your class as well. ::edit:: two years later… Don’t ever use PowerMockito, you shouldn’t need to. If you do need to, you have most likely broken the SOLID principles and your design is wrong. Fix your design instead.
This pom worked for me: <build> <finalName>final-name</finalName> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.8</source> <target>1.8</target> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.18.1</version> <configuration> <systemPropertyVariables> <jacoco-agent.destfile>target/jacoco.exec</jacoco-agent.destfile> </systemPropertyVariables> </configuration> </plugin> <plugin> <groupId>org.jacoco</groupId> <artifactId>jacoco-maven-plugin</artifactId> <version>0.7.2.201409121644</version> <executions> <execution> <id>default-instrument</id> <goals> <goal>instrument</goal> </goals> </execution> <execution> <id>default-restore-instrumented-classes</id> <goals> <goal>restore-instrumented-classes</goal> </goals> </execution> <execution> <id>default-report</id> <phase>prepare-package</phase> <goals> <goal>report</goal> </goals> </execution> </executions> </plugin> </plugins> </build> See this … Read more
I just solved this one now, when I added the @RunWith(PowerMockRunner.class) attribute, eclipse automatically imported: import org.powermock.modules.junit4.legacy.PowerMockRunner; All I needed to do is change it to be: import org.powermock.modules.junit4.PowerMockRunner; And now it works fine with JUnit 4.8.2. The 2nd runner is for when running with older versions of JUnit – specifically 4.3 and older.
If you are using Spring (the spring-test library specifically), you can simply use ReflectionTestUtils.setField instead of Whitebox.setInternalState
PowerMockRunner is part of powermock-module-junit4.jar. You need to explicity import this jar You could specify the dependency for this jar as per your requirement. Refer to this link.
What are you looking for is called partial mocking. In PowerMock you can use mockStaticPartial method. In PowerMockito you can use stubbing, which will stub only the method defined and leave other unchanged: PowerMockito.stub(PowerMockito.method(StaticUtilClass.class, “someStaticMethod”)).toReturn(5); also don’t forget about the @PrepareForTest(StaticUtilClass.class)
I had the same issue. Unfortunately it would not let me use a PowerMock Rule due to the JVM I had. Instead of the rule I used RunnerDelegate. @RunWith(PowerMockRunner.class) @PowerMockRunnerDelegate(Parameterized.class)
I’m posting in order to help future readers, you need to add these dependencies for powermock in AS testImplementation ‘junit:junit:4.12’ testImplementation ‘org.powermock:powermock-api-mockito:1.6.2’ testImplementation ‘org.powermock:powermock-module-junit4-rule-agent:1.6.2’ testImplementation ‘org.powermock:powermock-module-junit4-rule:1.6.2’ testImplementation ‘org.powermock:powermock-module-junit4:1.6.2’