[TIP] cleanUp for unittest
michael at quuxo.com
Sat Apr 4 04:58:45 PDT 2009
On Fri, 2009-04-03 at 19:52 +0100, Michael Foord wrote:
> Hmm... I disagree. I think most resource cleanup and deallocation can
> usually be expressed as a callable. What makes you think it is for a
> particular use case.
It might not be for a particular use case, but it is definitely for a
particular programming style.
Please add cleanUp() and deprecate tearDown(), but please don't force
everyone use a list of callables implementing fixture clean up. That
belongs in your project's inevitable common test superclass.
Michael Gratton <michael at quuxo.com>
Quuxo Software <http://web.quuxo.com/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.idyll.org/pipermail/testing-in-python/attachments/20090404/8f74a416/attachment.pgp
More information about the testing-in-python