[Chicago] ANN: Fudge: python mock / stub framework

Ian Bicking ianb at colorstudy.com
Tue Feb 3 20:18:18 CET 2009

On Tue, Feb 3, 2009 at 11:50 AM, Kumar McMillan <kumar.mcmillan at gmail.com>wrote:

> Hi all
> (sorry about the x-post ye Thunderbird users)
> I'm excited to announced the release of Fudge, a Python module for
> replacing real objects with fakes (mocks, stubs, etc) while testing.
> http://farmdev.com/projects/fudge/
> http://pypi.python.org/pypi/fudge
> Fudge started when a co-worker introduced me to Mocha [1], a mocking
> framework for Ruby and a simpler version of jMock (Java).  More
> rambling about all that is here:
> http://farmdev.com/thoughts/70/fudge-another-python-mock-framework/
> Yes, I know it's yet another mock framework.  I talk about how Fudge
> compares to the others here:
> http://farmdev.com/projects/fudge/why-fudge.html

In the latest release of minimock (1.1) instead of simply logging everything
to stdout, it can write to a MockTracker, and you can use it from unittest.

It doesn't deal with expectations directly, but I'm not sure what that would
add over checking that expectations after the run?  I guess that's the same
criticism as for mock?

Looking at pyMock, I wonder if the clever use of sys.settrace could be used
for some not-quite-mocking tests, especially applying tests to code that
wasn't written to be testable.

Ian Bicking  |  http://blog.ianbicking.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20090203/896aa5ff/attachment.htm>

More information about the Chicago mailing list