You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm always frustrated when I have to use multiple verifyNoMoreInteractions and verifyZeroInteractions calls for different mocks in my tests. It would be more efficient and readable if these methods could accept a list of mocks.
I would like the verifyNoMoreInteractions and verifyZeroInteractions methods to support passing a list of mocks. This way, we can verify multiple mocks in a single call, making the test code cleaner and easier to maintain.
An alternative solution would be to create a custom helper function in my own test code to loop through the mocks and call verifyNoMoreInteractions or verifyZeroInteractions on each one. However, having this functionality built into the Mocktail package would be more convenient and beneficial for all users.
Here is an example of a test case where multiple verifyNoMoreInteractions and verifyZeroInteractions calls are used:
To avoid using multiple verifyNoMoreInteractions and verifyZeroInteractions, my suggestion is to add support for passing a list of mocks to these methods.
I'm always frustrated when I have to use multiple verifyNoMoreInteractions and verifyZeroInteractions calls for different mocks in my tests. It would be more efficient and readable if these methods could accept a list of mocks.
I would like the verifyNoMoreInteractions and verifyZeroInteractions methods to support passing a list of mocks. This way, we can verify multiple mocks in a single call, making the test code cleaner and easier to maintain.
An alternative solution would be to create a custom helper function in my own test code to loop through the mocks and call verifyNoMoreInteractions or verifyZeroInteractions on each one. However, having this functionality built into the Mocktail package would be more convenient and beneficial for all users.
Here is an example of a test case where multiple verifyNoMoreInteractions and verifyZeroInteractions calls are used:
To avoid using multiple verifyNoMoreInteractions and verifyZeroInteractions, my suggestion is to add support for passing a list of mocks to these methods.
The text was updated successfully, but these errors were encountered: