Marcus Ilgner
08/11/2023, 9:41 AMcoEvery
, coVerify
and the class under test that tries to use the mock) ends up calling the actual implementation (verified by setting a breakpoint) and breaking because the mocked class actually hasn't been initialised at all (as one would expect). Having used mockk extensively in the past, the only explanation I can think of at the moment is that this is the only project with Kotlin 1.9.0 which, contrary to 1.8.20, isn't mentioned in the release notes anywhere.Marcus Ilgner
08/11/2023, 9:59 AMNonEmptySet
(Arrow 1.2) to a regular Set
, the class can be mocked just fine. Gonna create an issue for it and try to come up with a minimal reproducer.Marcus Ilgner
08/11/2023, 11:00 AM