<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns="http://usefulinc.com/ns/doap#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><Project><name>mock</name>
<shortdesc>A Python Mocking and Patching Library for Testing</shortdesc>
<description>There are already several Python mocking libraries available, so why another one?

Most mocking libraries follow the 'record -&gt; replay' pattern of mocking. I
prefer the 'action -&gt; assertion' pattern, which is more readable and intuitive
particularly when working with the Python `unittest module
&lt;http://docs.python.org/lib/module-unittest.html&gt;`_. For a discussion of the
merits of the two approaches, see `Mocking, Patching, Stubbing: all that Stuff
&lt;http://www.voidspace.org.uk/python/articles/mocking.shtml&gt;`_.

``mock`` provides a core ``Mock`` class that is intended to reduce the need to
create a host of trivial stubs throughout your test suite. After performing an
action, you can make assertions about which methods / attributes were used and
arguments they were called with. You can also specify return values and set
specific attributes in the normal way.

It also provides a ``patch`` decorator that handles patching module and class
level attributes within the scope of a test, along with ``sentinel`` for 
creating unique objects.</description>
<download-page>http://www.voidspace.org.uk/downloads/mock-0.6.0.zip</download-page>
<homepage rdf:resource="http://www.voidspace.org.uk/python/mock/" />
<maintainer><foaf:Person><foaf:name>Michael Foord</foaf:name>
<foaf:mbox_sha1sum>3c028684c0036c8ed14e2355d0dae4d1add4da2c</foaf:mbox_sha1sum></foaf:Person></maintainer>
<release><Version><revision>0.6.0</revision></Version></release>
</Project></rdf:RDF>