Niek Haarman edited this page Jan 3, 2018
·
16 revisions
- Will this library help mocking closed (non-open) classes?
- Will this library help overcoming NullPointerExceptions?
- I get an error ‘Resolved versions for app (1.1.x) and test app (1.0.x) differ’. What should I do?
Q: Will this library help mocking closed (non-open) classes?
A: Mockito-Kotlin does not really add any extra functionality to Mockito. As such, you will still get exceptions when trying to mock closed classes. If possible, try to use interfaces instead.
Mockito provides an incubating, opt-in feature to enable mocking closed classes. See Mock the unmockable for more details.
Q: Will this library help overcoming NullPointerExceptions with Mockito.any()?
A: Passing Mockito.any() to a non-nullable parameter in Kotlin fails with a NullPointerException. See Parameter specified as non-null is null.
Q: I get an error ‘Resolved versions for app (1.1.x) and test app (1.0.x) differ’. What should I do?
A: See Conflict with dependency
Q: Will this library support Mockito 1.x?
A: No. Mockito 2.x is officially released and this library will focus on these versions.