-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Mockito.after() method #91
Comments
I still like the |
In this case, I'd rather have a single opinionated method (unless I'm convinced otherwise :). How about this: mock(foo, after(10).times(2)).bar() It feels that 'after' has higher chance of producing ambiguous looking test code. |
Also, 'after' can be interpreted as:
AFAIR the implementation does not work this way. The impl expects the invocation(s) 'during' this time :) |
ok I agree, I now remember what this call did. Never mind my original comment. However, looking at your example, it would feel better if an alias could support mock(foo, during(10).times(2)).bar()
mock(foo, during(10, SECONDS).times(2)).bar() |
Yeah, this kind of alias makes perfect sense. |
Improve argument captors
Document Mockito.after() method. Add TODO that we should rename it in 2.0 into 'during'
The text was updated successfully, but these errors were encountered: