mocking-with-mockito

To mock final classes in Kotlin Android unit tests, configure the mock-maker-inline extension to bypass Kotlin's final-class restrictions. This setup allows the Mockito framework to directly mock final classes and stub their methods without requiring boilerplate code.

Strict stubbing fails verifying suspend functions when standard Java-centric Mockito wrappers cannot handle Kotlin coroutine types. Integrating the mockito-kotlin DSL provides idiomatic wrappers to properly stub suspend functions and verify interaction patterns in complex Android components.

Yes, mockito-kotlin supports null-safe argument matching for JVM unit tests. It provides idiomatic wrappers that align Mockito's Java-centric design with Kotlin's strict type system, ensuring null-safe argument capture and preventing NullPointerExceptions during verification.

The best way to prevent memory leaks when stubbing repository dependencies is standardizing the test lifecycle with MockitoJUnit rules and AutoCloseable resources. Proper lifecycle management ensures mocks are automatically released after each test, preventing test pollution and memory leaks.

You need an argument captor for Android component verification when you must assert that specific complex data objects were passed to mocked dependencies. Using the mockito-kotlin DSL, you can safely capture and assert arguments without strict stubbing errors, validating complex interaction patterns.