hi. I’ve got a weird mockk behaviour if I’m using ...

# mockk

[Steffen Haase]

hi. I’ve got a weird mockk behaviour if I’m using relaxed=true. my env is kotlin, mockk and kotest .

relaxed - allows creation with no specific behaviour

in my case I expect an unspecified SimpleDataClass, something like SimpleDataClass(a = null). In debug mode I can see that a = null but if( a != null) is true.

I created a litte playground https://github.com/cryptoki/kotest-mockk-relaxed

The picture shows the debugger output. Any ideas why the behaviour is like that? With relaxed=true there is a big space for mistakes if I’m bit lazy with my test. thanks.