Better error message if `Mockery.teardown` is called when `Mockery.setup` has not been called successfully
floehopper opened this issue · comments
This seems to have happened to at least a couple of people in relation to Rails fixtures - see #611. I think we could probably provide a more useful error message if Mockery.instance
is not set.