Github user eiri commented on the pull request:
https://github.com/apache/couchdb-couch-log/pull/6#issuecomment-143291308
Hm, `meck:validate/1` just checks if the whole mocked module has been used
according to its expectations, i.e. that there was no calls with a wrong number
of arguments or calls to non-existing function etc.
I guess I can wrap each log level into its own suite with meck's load,
expect, assert, validate and unload to ensure that we are calling backend's `X`
function and nothing else, but my current test pretty much does the same thing,
just with less typing and bonus of validating that we are not doing the double
calls.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
