Are there any analogues Mockito.verifyNoMoreInteractions(), Mockito.verifyZeroInteractions() ? about mockk HOT 12 CLOSED

Released 1.5.4 should handle both your use-cases:

verifyAll { mock.call1() }
verify { mock wasNot Called }

Please check and close ticket if everything is OK

from mockk.

Hello. I have related problem.
I have mock with some methods. I want to be sure that method def will be called once and other methods will not be called:

verify(mock, only()).def()
verifyNoMoreInteractions(mock)

So i can't use solution of the issue:

//java.lang.AssertionError: Verification failed: Mock(#1) should not be called
verify(exactly = 1) { mock.def() }
verify { mock wasNot Called }

or

//java.lang.AssertionError: Verification failed: Mock(#1) should not be called
verifyAll { mock.def() }
verify { mock wasNot Called }

from mockk.

verifyNoMoreInteractions just finalizes un-ordered verification checks and verifies that nothing else was called except already verified. Basically in MockK DSL I have very similar construct verifySequence, but it additionally checks order.

So overall solution would introduce verifyAll following way:

verifyAll {
  a.call1()
  b.call2()
  c.call3()
}

This translates to following Mockito code:

verify(a).call1()
verify(b).call2()
verify(c).call3()
verifyNoMoreInteractions(a, b, c)

Basically this checks that there was only calls 1,2 and 3 and nothing else in arbitrary order for mocks a, b and c.

Regarding verifyZeroIntercation. My basic idea is following code:

verify {
  a wasNot Called
}

but than logically to add was Called

verify {
   a was Called
}

which means called some method at least once.

Then:

verify(atLeast = 5) {
   a was Called
}

which means called some method at least 5 times.

Or:

verify(atMost = 5) {
   a was Called
}

which means called some method at most 5 times.

And finally:

verifyOrder {
   a was Called
   b.def()
}

which means first some method of a was called then method of b called.

Similiar:

verifySequence {
   a was Called
   b.def()
}

which means first some method of a was called then method of b called and that is all interaction with mocks a and b.

Sorry for long read. I've checked the code and seems it requires few days/week effort to implement all that. I understand it's easy to just implement first two cases and other may be quite useless, but I need to think twice before starting.

from mockk.

Update: In case anyone tries to use verify { mock wasNot Called } to replace verifyZeroInteractions() but couldn't pass the test. The correct usage is confirmVerified(mock). See "Verification confirmation" section in https://mockk.io/

from mockk.

Check PR #2. You basically can verify call happened exactly 0 times

from mockk.

this works for verify(exactly = 0) { foo.bar() }
but it is not working for verify(exactly = 0) { foo } similarly Mockito.verifyNoMoreInteractions(foo)

from mockk.

Ok, I'll consider adding it. Probably in today's night release

from mockk.

And thanks for reporting. Maybe any suggestions on how to do that? Anything else to add?

from mockk.

Thx.
I think it's worth to see how this is implemented in Mockito
I just started using mockk, maybe later there will be more requests

from mockk.

from mockk.

Mayde, something like
verifyNoMoreInteractions(foo, bar, ...)
or

verifyNoMoreInteractions {
   foo
   bar
   ...
}

from mockk.

Thx! I'll check it out soon

from mockk.