| commit | 1262c198418fb07d1cd5713104f7c756885b7b25 | [log] [tgz] |
|---|---|---|
| author | Anton Keks <anton@azib.net> | Fri Feb 19 13:25:42 2016 +0200 |
| committer | Anton Keks <anton@azib.net> | Fri Feb 19 13:25:42 2016 +0200 |
| tree | 1820d5f8fbe6be1698ce1e6d9d3d87af9f523133 | |
| parent | f6f142ade26f7586028ef8a82a2d1f7b1d7b14b7 [diff] |
add deep stubs test
A small library that provides helper functions to work with Mockito in Kotlin.
Mockito-Kotlin is available on JCenter. For Gradle users, add the following to your build.gradle:
repositories { jcenter() } dependencies { testCompile "com.nhaarman:mockito-kotlin:x.x.x" }
Due to Kotlin‘s reified type parameters, if the type can be inferred, you don’t have to specify it explicitly:
Java:
MyClass c = mock(Myclass.class); c.doSomething(mock(MyOtherClass.class));
Kotlin:
val c : MyClass = mock() c.doSomething(mock())
If the type can't be inferred, you can pass it like so:
val d = mock<MyClass>()
Mockito‘s any(Class<T>) often returns null for non-primitive classes. In Kotlin, this can be a problem due to its null-safety feature. This library creates non-null instances when necessary. Again, if the type can be inferred, you don’t have to specify it explicitely:
Java:
verify(myClass).doSomething(any(String.class));
Kotlin:
verify(myClass).doSomething(any()); // Non-nullable parameter type is inferred
For generic arrays, use the anyArray() method:
verify(myClass).setItems(anyArray())
Using higher-order functions, you can write very clear expectations about expected values. For example:
Kotlin:
verify(myClass).setItems(argThat{ size == 2 })
Most of Mockito‘s static functions are available as top-level functions. That means, IDE’s like IntelliJ can easily import and autocomplete them, saving you the hassle of manually importing them.