CaptureMock 1.0 - true record/replay mocking for Python (and other things...)

Geoff Bache geoff.bache at gmail.com
Thu Apr 3 22:30:02 CEST 2014


Hi all,

CaptureMock has come of age at last and reached 1.0. Many things have been
fixed and improved since the last release. Notably:

- Supports python callbacks in a limited fashion (i.e. intercepted code
calling back into non-intercepted code)
    Makes it possible to e.g. intercept Tkinter and use CaptureMock for a
limited kind of GUI testing.
- Should work better in Python 3
- Mock files are more readable, we use pprint to ensure it doesn't get too
wide. Naming of "variables" is more intelligent and descriptive, make use
of strings provided when the objects first appear
- Client-server support now handles XMLRPC servers

Regards,
Geoff Bache

More detail:

CaptureMock is a tool for creating mocks via a "true" capture-replay
style approach. It records interactions to a separate file which can
then be used for replay in future runs. It is thus not another
"EasyMock" clone. Interaction can be recaptured from a real
system at any point, and no mock code needs to be written. It handles
Python calls, command-line programs, and synchronous messaging over
networks. Custom clients can now also be written for any language.

Website: http://www.texttest.org/index.php?page=capturemock
Examples: https://github.com/msabramo/capturemock_examples/
Mailing list: https://lists.sourceforge.net/lists/listinfo/texttest-users


More information about the Python-announce-list mailing list