<Mokkery> updates! Changes since my last post here...

# feed

[Damian Baczyński]

Mokkery updates!
Changes since my last post here:
• Improved verification errors to be more informative
• Shorter mock names in verification output
• Wasm-WASI support (without coroutines)
• New documentation website
• New answers - sequentiallyRepeat and throwsErrorWith
• New matchers - notNull and matchingBy
• New AutofillProvider API
• Fix of a bug that prevented mocking functions returning value classes
• Pre-release with Kotlin 2.0.0-Beta5

[MrNiamh]

You mention Mockk in your github, but it would be useful to know what exactly you provide that Mockk doesn't

[Damian Baczyński]

It mentions MockK because Mokkery shares syntactic similarities, making it familiar to MockK users. However, both libraries target different groups of users. Mokkery should be more suitable for Multiplatform projects, while MockK in practice is JVM only library. That's why there is no such a comparison in README. However, I can give you a quick summary here:
• Mokkery supports all multiplatform targets, while MockK only supports JVM and JS targets.
• MockK allows mocking of static declarations, unlike Mokkery, which doesn't support it, because as far as I know it is not possible for non-JVM targets.
• MockK primarily operates at runtime, whereas Mokkery performs a significant portion of its work at compile time.