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
In Mockito, when using verify() you get a list of all the interactions with a mock on a failure.
So the use cases would be:
var func = mockFunction();
func('abc');
verify(func)('def');
// Prints the following:
// Wanted but not invoked: func('def')
// However, there were these interactions:
// --> func('abc')
var func = mockFunction();
func('abc');
func('def');
verifyNoInteractions(func);
// Prints the following:
// Wanted not invoked: func('abc')
// However, there were these interactions:
// --> func('abc')
// --> func('def')
etc.
I've been prototyping this change and it doesn't look too hard, I've just run into some problems running the unit tests (the browser locks up). Should I be using ant to run them?
The text was updated successfully, but these errors were encountered:
You can use Ant, or just run them in the browser. I haven't worked on JsMockito in some time, and it was written back when the only real headless option was Rhino. It would be ideal to re-package it (and probably rewrite the unit tests) to run on node.js now. At some point I may find the time to do that!
In Mockito, when using verify() you get a list of all the interactions with a mock on a failure.
So the use cases would be:
etc.
I've been prototyping this change and it doesn't look too hard, I've just run into some problems running the unit tests (the browser locks up). Should I be using ant to run them?
The text was updated successfully, but these errors were encountered: