Dale King
Dale King
I would like to have a way to be notified of invocations on mocks. The main purpose for doing this is to log mock invocations to better debug test failures,...
The migration guide says this: https://github.com/mockative/mockative/blob/main/wiki/MIGRATING-TO-2.md#implicit-stubbing-of-unit-returning-functions That may have been true in early versions of V2 but is no longer true today. The text here needs to be updated to...
The way you have the Funx types set up to allow for mocking functions is slightly verbose for setting up the mocks. If you turn the types into fun interfaces...
I have a test where I had a coVerify block and actually forgot to put the call to the method and the error you get is just a NullPointerException. You...
It seems to me that it would be possible to just have every and verify and through overloads or internally it would be possible to handle the distinction without requiring...
I have tests where the object being tested does a bunch of initialization which can make calls on the mocks any number of times. I then want to test what...
I would like to see a global call back mechanism to monitor calls to mocks and possibly even modify the behavior. One use for this would be for logging. In...
The new lambda function doesn't pass CallArgs so you cannot build the returned value based on passed arguments
The docs say you can do this: ``` import dev.mokkery.gradle.mokkery dependencies { implementation(mokkery("coroutines")) // defaults to the current Mokkery version } ``` but i get: > Type mismatch: inferred type...
In most of my use of Mocking I set up mocks without checking parameters of the call in the setup and instead check parameters in verification. It would be nice...