Mattia Tommasone

Please, do! There are some issues already open specifically for KMM / Kotlin native, which may be a good starting point for contributing.

Looks like a bug indeed. Out of curiosity, why are you running `confirmVerified` on `arg`? is it to make sure that no interactions were performed with it? It's also worth...

Still relevant indeed, although I don't think it will be easy to discriminate calls to equals that need to be recorded from calls that should not.

Thanks for submitting this, it is indeed a regression. While I look into it, as a workaround, you can use `constructedWith()` instead of `anyConstructed()` and the test will pass.

I think the best workaround here would be to mock the `DecisionRepository` rather than the `OfferService` and provide a mocked behavior for `latestByApplication`.

I don't think you can `spyk` an interface, since spies try to execute the actual methods of the objects being spied, it's probably better to `mockk` it.

Looks like this is an actual bug, `static` blocks likely need to be handled specifically.

Not sure if this applies to your case since your example is minimized, but: do you really need to mock the `AndroidData` class? If it's a data class, or a...

(also, note that capturing can also be used in `verify` blocks)

Since your inner object is being instantiated internally, you need to mock the `SomeFieldType` constructor to have it return a mock: ``` class SomeClassTest { @Test fun `test method`() {...