it seems that <a recommended way to mock extensions with Mockk> is to define a `@file:JvmName` and r...

# mockk

[diego-gomez-olvera]

it seems that a recommended way to mock extensions with Mockk is to define a @file:JvmName and refer to it with mockkStatic("<jvm-name>"), which is not type safe: In case of refactoring (e.g. rename or package change), the tests might break inadvertently. Is there a more type safe manner to mock extension functions?

[diego-gomez-olvera]

also shared in StackOverflow https://stackoverflow.com/questions/69284408/typesafe-way-to-use-mockk-and-extension-functions

[Mattia Tommasone]

yes, it’s a relatively recent addition: https://mockk.io/#extension-functions

[Mattia Tommasone]

you can use either

mockkStatic(Obj::extensionFunc)

or

@file:JvmName("KHttp")

which has indeed the problem that it is not safe towards class renaming, you’re right

[diego-gomez-olvera]

ah, I like the alternative using the method reference. It is potentially more code to write (for several extensions), but also more robust

[diego-gomez-olvera]

thanks!

[Justin Tullgren]

just ran into this, good alternative