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
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.
The text was updated successfully, but these errors were encountered:
Although history/1 should probably be left since people might want to build their own hacks on top of it (but with the documented caveat that the return format might change in future versions).
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:
That probably covers everything a testing human being might need.
The text was updated successfully, but these errors were encountered: