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 r.david.murray
Recipients michael.henry, r.david.murray, santoso.wijaya
Date 2011-03-18.19:42:42
SpamBayes Score 5.8263104e-05
Marked as misclassified No
Message-id <1300477363.15.0.915245446869.issue11589@psf.upfronthosting.co.za>
In-reply-to
Content
Until unittest learns to do parameterized tests, it's nice to have each test be separate so that you can easily see which test cases are failing.  (A number of the existing email tests have a lot of tests in each "unit" test, and this can make debugging more difficult, as I know well.)

I've been known to synthesize parameterized tests in my unit tests to save myself some typing, but Michael has already done the typing here...
History
Date User Action Args
2011-03-18 19:42:43r.david.murraysetrecipients: + r.david.murray, santoso.wijaya, michael.henry
2011-03-18 19:42:43r.david.murraysetmessageid: <1300477363.15.0.915245446869.issue11589@psf.upfronthosting.co.za>
2011-03-18 19:42:42r.david.murraylinkissue11589 messages
2011-03-18 19:42:42r.david.murraycreate