This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vdupras
Recipients vdupras
Date 2008-02-21.16:11:34
SpamBayes Score 0.17266259
Marked as misclassified No
Message-id <1203610296.31.0.753914026052.issue2156@psf.upfronthosting.co.za>
In-reply-to
Content
I've been using unittest for quite a while. One thing I got tired with is 
the code duplication for file management and mocking. A few months ago I 
created this nifty little TestCase subclass and I've been using it ever 
since. It works quite well.

Am I the only one to extensively use temporary files and mocking in my 
tests? If not, I would suggest integrating my little subclass to 
unittest.Testcase, or if people think these functionalities out-scope 
unittest.TestCase, maybe we could put it in a separate unit.

Here's the unit I have here.
History
Date User Action Args
2008-02-21 16:11:36vduprassetspambayes_score: 0.172663 -> 0.17266259
recipients: + vdupras
2008-02-21 16:11:36vduprassetspambayes_score: 0.172663 -> 0.172663
messageid: <1203610296.31.0.753914026052.issue2156@psf.upfronthosting.co.za>
2008-02-21 16:11:35vdupraslinkissue2156 messages
2008-02-21 16:11:35vduprascreate