[TIP] Fwd: cleanUp for unittest
dgou at mac.com
Fri Apr 3 13:18:56 PDT 2009
On or about Friday, April 03, 2009, at 04:01PM, Michael Foord indited:
>The implementation and usage is all clean and straightforward to
>understand, which again are points in its favour. Resource allocation /
>deallocation is something that it is easy to get wrong in testing, this
>makes it easier.
(Perhaps my previous reply was eaten by a grue.)
I think having this an tearDown is a recipe for confusion.
Can you explain how this interacts with tearDown, specifically, if I have this, why would I ever put anything into tearDown?
More information about the testing-in-python