Mocking Static Methods and Constructors

Welcome! So far, you've learned to mock interfaces and regular classes using Mockito. But what about those tricky bits of code that seem resistant to testing?

Sometimes, you encounter static methods, final classes, or direct constructor calls (new MyObject()) within the code you want to test. Standard Mockito can't handle these directly.

Why do we need to mock these?

• Static utility methods: Often used for common tasks, but hard to isolate if they have side effects or external dependencies.
• Final classes/methods: Cannot be subclassed or overridden, making traditional proxy-based mocking impossible.
• Constructor calls (new): Direct object creation within a method makes it hard to inject a mock instead.

Mocking these helps you isolate the code under test, even in complex or legacy systems.