A tool for creating mocks via a capture-replay style approach
CaptureMock’s approach is a so-called capture-replay approach. This means that when you ‘record’ your mock, CaptureMock will observe the interaction between your code and the subsystem you are mocking out, and record it in a text file in its own format. When you then run your test in ‘replay mode’, CaptureMock can play the role of the subsystem in question and the real subsystem does not need to even be installed.
You can then choose, each time you run your tests, whether you wish to have the real subsystems present and verify/recreate the captured mocks, or to rely on the mocks captured by a previous run. If you are running in ‘replay mode’ and CaptureMock does not receive the same calls as previously, it will fail the test, and suggest that you may want to recreate the mocks in record mode.