使用TestNG+Mockito+PowerMock测试含静态/终态类时持续报ClassNotPreparedException

Hey there, let's dig into this org.powermock.api.mockito.ClassNotPreparedException issue you're facing with PowerMock, TestNG and your JeebiesKwCheckUtil class. I've dealt with this exact frustration before, so let's break down the most common fixes that often get missed even when following the official docs:

1. Double-check TestNG & PowerMock Version Compatibility #

PowerMock is picky about version matches with TestNG. For example, PowerMock 2.x requires TestNG 6.11 or newer. If your pom has mismatched versions, this exception is almost guaranteed. Here's a compatible dependency snippet to reference:

<dependency>
    <groupId>org.powermock</groupId>
    <artifactId>powermock-module-testng</artifactId>
    <version>2.0.9</version>
    <scope>test</scope>
</dependency>
<dependency>
    <groupId>org.testng</groupId>
    <artifactId>testng</artifactId>
    <version>7.4.0</version>
    <scope>test</scope>
</dependency>

2. Don't Forget to Hook PowerMock into TestNG #

For TestNG, just adding @PrepareForTest isn't enough. You need to either:

• Extend PowerMockTestCase in your test class:

  @PrepareForTest(JeebiesKwCheckUtil.class)
  public class JeebiesKwCheckUtilTest extends PowerMockTestCase {
      // Your test methods here
  }
  

• Or use the @PowerMockListener annotation if you don't want to inherit a class:

  @PrepareForTest(JeebiesKwCheckUtil.class)
  @PowerMockListener(TestNGPowerMockListener.class)
  public class JeebiesKwCheckUtilTest {
      // Your test methods here
  }
  

3. Include Dependent Static Classes in @PrepareForTest #

If JeebiesKwCheckUtil's static methods call other static classes, you need to prepare those too. For example, if it uses StaticHelperClass.doSomething(), update your annotation:

@PrepareForTest({JeebiesKwCheckUtil.class, StaticHelperClass.class})

4. Verify PowerMock-Mockito Integration Dependencies #

Make sure you're using the correct PowerMock-Mockito bridge for your Mockito version. For Mockito 2.x/3.x, include this:

<dependency>
    <groupId>org.powermock</groupId>
    <artifactId>powermock-api-mockito2</artifactId>
    <version>2.0.9</version>
    <scope>test</scope>
</dependency>

5. Clean Up Conflicting Annotations #

Double-check that your test class doesn't accidentally have JUnit-specific annotations like @RunWith—even if you're using TestNG, these can cause PowerMock to misbehave.

6. Reset Your Build Environment #

Sometimes IDE caches or corrupted dependency jars are the culprit. Run mvn clean install -DskipTests to wipe old builds and refresh dependencies, then re-run your tests.

7. Handle Final Members Properly #

For final static fields in JeebiesKwCheckUtil, use PowerMock's Whitebox utility to set their values instead of regular Mockito methods:

Whitebox.setInternalState(JeebiesKwCheckUtil.class, "yourFinalStaticField", "testValue");

Full Example Test Class #

Here's a complete example tying all these pieces together:

import org.powermock.api.mockito.PowerMockito;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.testng.PowerMockTestCase;
import org.powermock.reflect.Whitebox;
import org.testng.annotations.Test;

@PrepareForTest(JeebiesKwCheckUtil.class)
public class JeebiesKwCheckUtilTest extends PowerMockTestCase {

    @Test
    public void testStaticMethodBehavior() {
        // Mock the static method
        PowerMockito.mockStatic(JeebiesKwCheckUtil.class);
        PowerMockito.when(JeebiesKwCheckUtil.yourStaticMethod()).thenReturn("expectedResult");

        // Execute your test logic here
        String result = JeebiesKwCheckUtil.yourStaticMethod();

        // Verify the static method was called
        PowerMockito.verifyStatic(JeebiesKwCheckUtil.class);
        JeebiesKwCheckUtil.yourStaticMethod();
    }

    @Test
    public void testFinalFieldImpact() {
        // Set the final static field
        Whitebox.setInternalState(JeebiesKwCheckUtil.class, "finalStaticField", "testValue");

        // Run your test that depends on this field
        // ...
    }
}

内容的提问来源于stack exchange，提问作者Felix