[TIP] cleanUp for unittest

Olemis Lang olemis at gmail.com
Fri Apr 3 11:52:37 PDT 2009


On Fri, Apr 3, 2009 at 12:16 PM, Michael Foord
<fuzzyman at voidspace.org.uk> wrote:
> C. Titus Brown wrote:
>> On Fri, Apr 03, 2009 at 06:08:58PM +0100, Michael Foord wrote:
>> -> There is a feature request for unittest that we add a 'cleanUp' list.
>> ->
>> -> This is a list of functions to call on exit of a test that can be added
>> -> to in setUp or during test execution. The difference between this and
>> -> tearDown is that if anything is in the cleanUp list they will be called
>> -> *even* if setUp fails (which normally means tearDown is skipped).
>> ->
>> -> Is there consensus that adding this to unittest is a good thing? If
>> -> there is then I will just do it...
>> ->
>> -> Should it be done before or after calling tearDown? I don't think it
>> -> matters so long as it is documented.
>>
>> Doesn't matter to me, but I'm wondering... why a list of functions?
>>
>> --titus
>>
> I should have listed the relevant issue: http://bugs.python.org/issue5538
>
> The idea is that as you allocate resources that need cleaning up, you
> push the corresponding clean up function onto the list. It is what trial
> uses.
>
> It sounds like a very simple system to me.
>

My initial position is as follows unittest is a framework inheriting
well-known features present in many similar testing framews for many
languages ... I think that unittest.TestCase should include nothing
but the really simple, common and crucial features for defining test
cases according to XUnit paradigm ... And should be kept as stable as
possible ...

Q: I'd like to know if there is another XUnit framew for another
language providing such a functionality in core ...

Q: I'd like to know how many use cases in stdlib test suite can
benefit from this feature ...

I do think this is helpful ... I dont think it should be included in
unittest.TestCase ... you'll get a +1 from me if you do that in a
subclass of unittest.TestCase which can be also in stdlib ...

I see this more like a testing pattern ... AFAICR there's something
like this in XUnit patterns book and still this is not in JUNit's
TestCase class, or similar, AFAIK ...

Pls ... CMIIW anyway ...

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:
Comandos : Pipe Viewer ... ¿Qué está pasando por esta tubería?



More information about the testing-in-python mailing list