In 1.12.3 `verify { mock.method( withArg {}) }` fails if second call matches. Works in 1.12.2

Prerequisites

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Expected Behavior

When calling verification using withArg{}, if there are multiple calls to mock method, and one of calls matches withArg, the verification should pass.

Current Behavior

If there are multiple calls to method verification will fail. It passed in 1.12.2

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• MockK version: 1.12.3
• OS: Win/Linux
• Kotlin version: 1.6.10
• JDK version: 17-azul
• JUnit version: 5.8.2
• Unit Test

Minimal reproducible code (the gist of this issue)

@Test
fun `mockk can assert one of calls`() {
    open class Mocked {
        fun called(i: Int) {}
    }
    val mock = mockk<Mocked>()
    every { mock.called(any()) } just Runs
    mock.called(1)
    mock.called(3)
    verify {
        mock.called(withArg { assert(it == 3) })
    }
}

I would guess this is caused by https://github.com/mockk/mockk/pull/776, as https://github.com/mockk/mockk/pull/394 fixed https://github.com/mockk/mockk/issues/389 that seemed similar, and https://github.com/mockk/mockk/pull/776 reverted changes.

If this is intentional change, please provide intended way of asserting with many calls.

[Raibaz]

As a side note, most of the code that I have seen doing

verify {
    mock.method(withArg {
        assertEquals("someValue", it.property)
    })
}

Can also be written as

verify {
    mock.method(match {
        it.property == "someValue"
    })
}

Which is, IMHO, pretty concise for a few properties to be checked.

In case someone needs to verify more than a few properties, I’d probably still go for a slot.

[piotrplazienski]

Yes, I think using predicate is better practice and that is where I will go with rework of my tests.

I will close the issue now.