“Kotlin Unit Testing with Mockk” by Marco Cattaneo.Unraveling MockK’s black magic(EN, translation).Unraveling MockK’s black magic / MockKの「黒魔術」を解明する (JP, but readable through chrome translator).Testing Quarkus with Kotlin, JUnit and MockK.Private functions mocking / dynamic calls.Verification atLeast, atMost or exactly times.Mock relaxed for functions returning Unit.Spies, mockkStatic may not work on JDK 16+ InaccessibleObjectException/ IllegalAccessException: read more here.Inline functions cannot be mocked: see the discussion on this issue.(not sure after workaround if it is generally usable or not, please somebody report it) PowerMock needs a workaround to run together with MockK #79.Documentation can be found hereįrom version 1.13.0 MockK supports Kotlin 1.4 and higher Known issues quarkus-mockk adds support for mocking beans in Quarkus.springmockk introduced in official Spring Boot Kotlin tutorial.Expected behavior and behavior verification.Academy describing MockK from the very basics of mocking up to description of all advanced features. (Although you generally shouldn’t need to access so deeply into a class! Still, reducing the number of safe-calls can help readability).Check the series of articles “Mocking is not rocket science” at Kt.
Let’s get on with it, shall we? For 2 or more constructor arguments, prefer not to keep the properties on the same line as the class name in the constructor definition class M圜lass ( val a: A, val b: B, ): MyParentClass(a, b), MyInterface Hopefully, the following tips and style recommendations (in no particular order) will help you write better Kotlin!
I’ve been meaning to write this article in a while.
0 kommentar(er)
