mocks seem to persist outside of use_cassette blocks about exvcr HOT 3 CLOSED

Thank you for the report. In the current implementation, :meck calls are spanned across test cases and would be causing this error.

When I initially tried, :meck.unload was taking time and unified some method calls. I'll re-verify the time, and at least try to add a switch to ensure unloading inside the use_cassette block.

from exvcr.

I've added an option (clear_mock: true) to call :meck.unload for each use_cassette block as in the above test case (simplex_test.exs).
It may be expected to be called every time by default, but I'm leaving it as optional at the momemnt, since the testing seems to take twice in my environment (haven't been able to find a good solution on this point).

from exvcr.

Please let me close this item. If you find any further comments, please reopen or open another one.

from exvcr.