If you're looking to accomplish something with Mocktail that doesn't involve test-driven development, let's get real. There's a very high likelihood that what you're looking to do is either:
- Not the best tool for the job
- Not a job worth doing
But hey, could be wrong. The present author once did a talk about all the ways people abuse mocking libraries and undermine the value of their tests, so there is a track record of bias here.
By popular demand, here are some ways you might be thinking about using Mocktail:
Mocking out the system clock in a vain attempt to master space and time.
Mocking an HTTP API by faking out Ruby's built-in networking.
Mocking out just one method on an otherwise real object.
Recording method invocations while calling through to their real implementation.
Using Mocktail to fix an existing test that's failing in a gnarly way you don't understand.
Mocking out a method on the subject under test, AKA the thing you're testing itself.
Once you've seen enough, you can take a second look at Mocktail as a TDD tool.