Testing
Mockito is the default choice for mocking in Java tests. It's clean, composable, and integrates naturally with JUnit 5. Most of the time, it's all you need. But Mockito has hard limits — it cannot mock static methods (without extensions), final classes, constructors, or private methods. That&
Testing
Static methods are the hardest thing to mock in Java. They're called directly on the class, not on an injected instance, so standard mocking frameworks — which work by creating proxy subclasses — can't intercept them. That's why two separate solutions exist: PowerMock's mockStatic(
Testing
PowerMock exists because Mockito has hard limits. Mockito cannot mock constructors, cannot intercept new calls inside a method under test, and cannot directly invoke private methods for assertion. PowerMock lifts those limits by bytecode-manipulating your classes at test time. That power comes with real costs — complexity, classloader isolation, slow
Testing
Payment provider SDKs make real HTTP calls that cost money, have rate limits, and behave differently in different environments.
Testing
An AI agent that manages your GitHub issues calls the GitHub API. An agent that schedules meetings calls Google Calendar.
gRPC
Mocking gRPC services in Java is more involved than mocking REST APIs.