|File Search||Catalog||Content Search|
In readable Python code, you declare what methods are available on your fake and how they should be called. Then you inject that into your application and start testing. This declarative approach means you don’t have to record and playback actions and you don’t have to inspect your fakes after running code. If the fake object was used incorrectly then you’ll see an informative exception message with a traceback that points to the culprit.
Fudge was inspired by Mocha which is a simpler version of jMock. But unlike Mocha, Fudge does not automatically hijack real objects; you explicitly patch them in your test. And unlike jMock, Fudge is only as strict about expectations as you want it to be. If the type of arguments sent to the fake method aren’t important then you don’t have to declare an expectation for them.
This is the documentation of python-fudge.
python-fudge (1.0.3-3) unstable; urgency=low * Fix "missing dependency on python3!!" by using correct variable in debian/control (Closes: #674405) * fix Vcs-Svn and Vcs-Browser URLs in debian/control -- Jan Dittberner <email@example.com> Thu, 24 May 2012 15:21:51 +0200 python-fudge (1.0.3-2) unstable; urgency=low * Fix "FTBFS if built twice in a row: aborting due to unexpected u more»
Format: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=174 Upstream-Name: fudge Upstream-Contact: Kumar McMillan http://farmdev.com/projects/fudge/ Source: http://pypi.python.org/pypi/fudge Files: * Copyright: Copyright (c) 2009 Kumar McMillan License: MIT Files: debian/* Copyright: Copyright (c) 2011 Jan Dittberner License: MIT License: MIT Permission is hereby granted, free o more»