Often fully featured mock objects are not appropriate for a testing problem. More...
|A base class to keep track of occurrences. More...|
|The master counter from which clients obtain the current occurence count. More...|
|The client counter to track occurrences based on a shared counter. More...|
Often fully featured mock objects are not appropriate for a testing problem.
In this case you can write your own mock objects with minimal functionality. Unfortunately such objects carry little or no additional information which makes it hard to find the cause and location of the problem.
For that reason mockpp contains some classes to address such simple problems which also provide some human readable information.
Call verify() at the end of a unit test to check for missing or incomplete values. If no expectations have been set on the object, then no checking will be done and verify() will do nothing.