Closed
Description
Test writers do not need entire history. They need a convenient way to find out some specific facts about the history like called and num_calls functions. By providing them entire history we kind of forcing them to write custom information retrieval and verification functions.
I believe a better way would be to provide a comprehancive set of history digging functions, such as:
- verify - a unified version of called and num_calls that allows complex number of calls verification, argument matching using standard Erlang patterns and possibly Hamcrest matchers. It will also support verification of the order in which functions were called;
- capture - provides a way to retrieve a particular argument value that a particular function was called with.
That probably covers everything a testing human being might need.