Comments on: Getting Started with MockK in Kotlin [1/5] https://blog.codersee.com/getting-started-with-mockk-kotlin/ Kotlin & Backend Tutorials - Learn Through Practice. Wed, 16 Apr 2025 04:49:36 +0000 hourly 1 By: Awais Zaka https://blog.codersee.com/getting-started-with-mockk-kotlin/#comment-109 Sun, 16 Mar 2025 11:56:53 +0000 https://codersee.com/?p=17512637#comment-109 Is MockK available for KMP?

]]> By: Piotr https://blog.codersee.com/getting-started-with-mockk-kotlin/#comment-108 Sun, 16 Mar 2025 09:01:36 +0000 https://codersee.com/?p=17512637#comment-108 In reply to Alexander Skvortsov.

I would debate the overall benefit of doing that on our own if we gather together all aspects, not only performance. But if it works for you / in your environment, then you should stick to that.

I am the last person to promote anything as one-size-fits-all.

Nevertheless, you must remember that even if we would agree that custom fakes/wrappers are always the way to go, we don’t always choose the stack, or have the impact on the approach taken in the project 😉

]]> By: Alexander Skvortsov https://blog.codersee.com/getting-started-with-mockk-kotlin/#comment-107 Sun, 16 Mar 2025 07:57:29 +0000 https://codersee.com/?p=17512637#comment-107 Why just don’t follow SOLID (and especially “Interface segregation” principle) to keep the code easy testable?
Fakes (and wrappers for 3rd party deps) extremely easy to do and they works a way faster then all those mocking libs. Again, no need to learn more API and libs and depend on them.

]]>