Say I have a verify block like this ```verify someMethod cap

Question

Say I have a verify block like this ```verify someMethod capture mySlot Some specific value ``` Is there any way to actually just capture the value from when someMethod was called with Some specific value Or will that capture match every single call even the ones where the whole expression doesn t match

ephemient · Answer

works on the mocking side

Patrick Ramsey · Answer

hmm

Patrick Ramsey · Answer

So say in the code under test someMethod ends up getting called twice

Patrick Ramsey · Answer

someMethod 3 Some specific value someMethod 4 some other string

ephemient · Answer

```val slot = mutableListOf lt T gt val obj = mockk justRun someMethod any any justRun someMethod capture slot eq Some specific value obj someMethod foo bar obj someMethod capture me Some specific value ```

Patrick Ramsey · Answer

you d expect mySlot to contain 3 but it ll actually be set to 4

ephemient · Answer

you could file an issue about it not working on the verify side but consider fixing it yourself

Patrick Ramsey · Answer

<https github com mockk mockk issues 352> so since posting I found this issue

ephemient · Answer

that s not the same thing

Patrick Ramsey · Answer

it looks like in more recent mockk it warns when you do this But unfortunately that still means there isn t to my knowledge a good way to match a certain call then get the arguments from that call

ephemient · Answer

and is why I used MutableList to capture

Patrick Ramsey · Answer

right but

ephemient · Answer

there is match it in mockk every justRun

Patrick Ramsey · Answer

if you use MutableList you just end up with a list of matched parameters right

ephemient · Answer

it s just the matchers in verify that don t seem to operate in the right order

Patrick Ramsey · Answer

you don t know which values corresponded to which calls

Patrick Ramsey · Answer

ah Let me see if I can structure this to do it from every

Patrick Ramsey · Answer

but just to make sure I understand using a capture in a verify block means you re effectively matching every call even if there are other matchers that are more specific

ephemient · Answer

found a ticket <https github com mockk mockk issues 408>

Patrick Ramsey · Answer

OOOO

Patrick Ramsey · Answer

awesome Okay

ephemient · Answer

yes it s a bug there s not enough manpower to fix mockk consider fixing it yourself

Patrick Ramsey · Answer

ok Good to know

Patrick Ramsey · Answer

thanks < ephemient>

Patrick Ramsey · Answer

sorry to bother you

ephemient · Answer

np hope matching in every is a usable workaround for the time being

ephemient · Answer

I don t work on mockk I just use it too and run into other issues

Patrick Ramsey · Answer

yeah I think so

Patrick Ramsey · Answer

and thank you for popping up and helping anyway slightly smiling face and I ll consider contributing a fix Would be nice to contribute back to a project I use every day slightly smiling face

Patrick Ramsey · Answer

thanks again and have a good night

Mattia Tommasone · Answer

thanks a lot to both of you for the discussion and the help slightly smiling face the behavior described in 408 indeed looks like what < Patrick Ramsey> is experiencing so basically `capture` should be capturing only calls that are actually matched by a verify block and not all calls It is indeed a bug i may try taking a shot at fixing it soon but if in the meantime you want to start looking into it i d be more than glad feel free to shoot any questions slightly smiling face