Fix wasNotshould throw exception when called on non mocked object

[Gosunet]

@Raibaz Here is to PR the fix #1155

I used the internalIsMockKMock with all parameters to true to check is the called object is a mock, please tell me if I miss something.
For the tests, I added some in a separate file, I wasn't sure where to put them.

Closes #1155

[Gosunet]

Also, I have two tests failing with this implementation:

• ConstructorMockTest.givenEmptyCallListInStubbingStateWhenRecordingDoneIsCalledThenExceptionIsThrown()
• ConstructorMockTest.clear, those test use wasNot on a non mocked object

[jcopenhop]

I think

mockk/modules/mockk/src/commonTest/kotlin/io/mockk/impl/recording/states/StubbingStateTest.kt

Line 28 in 9f19288

verify {

can be rewritten as verify(exactly = 0) { recorder.factories.stubbingAwaitingAnswerState(any()) }

similarly I think

mockk/modules/mockk/src/commonTest/kotlin/io/mockk/it/ConstructorMockTest.kt

Line 100 in 9f19288

verify { anyConstructed<MockCls>() wasNot Called }

can be
verify(exactly = 0) { anyConstructed<MockCls>() }

[Raibaz]

Re: the failing tests: I think you can rewrite them both as verify(exactly = 0) as @jcopenhop suggested.

[Gosunet]

It's working for the StubbingStateTest.kt as mentioned by @jcopenhop.

But replacing this:

verify { anyConstructed<MockCls>() wasNot Called } 

By this:

 verify(exactly = 0) { anyConstructed<MockCls>() }

Give me this error:

io.mockk.MockKException: Missing calls inside verify { ... } block.

[Raibaz]

That seems like a bug with anyConstructed.

I think we can just skip the test for now and temporarily accept that anyConstructed is not working with exactly at the moment.

Would you mind opening an issue about it, please?

[Gosunet]

Done #1224

I have ignore this test for now and link the issue to it.