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 ezio.melotti
Recipients Julian, Yaroslav.Halchenko, abingham, bfroehle, borja.ruiz, brian.curtin, chris.jerdonek, eric.araujo, eric.snow, exarkun, ezio.melotti, fperez, hpk, kynan, michael.foord, nchauvat, ncoghlan, pitrou, r.david.murray, santoso.wijaya, serhiy.storchaka, spiv
Date 2013-01-18.21:50:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I like the idea, and I think this would be a useful addition to unittest.

OTOH while this would be applicable to most of the tests (almost every test has a "for" loop to check valid/invalid values, or a few related "subtests" in the same test method), I'm not sure I would use it too often.
The reason is that often there's a single bug that causes the failure(s), and most likely the error reported by unittest is the same (or anyway it's very similar) for all the subtests, so using subtests would just add more noise (at least for me).
However it might be useful in case of sporadic failures or whenever having the full set of failures would be useful to diagnose the problem.
Date User Action Args
2013-01-18 21:50:18ezio.melottisetrecipients: + ezio.melotti, spiv, exarkun, ncoghlan, pitrou, eric.araujo, r.david.murray, michael.foord, brian.curtin, hpk, fperez, chris.jerdonek, Yaroslav.Halchenko, santoso.wijaya, nchauvat, kynan, Julian, abingham, eric.snow, serhiy.storchaka, borja.ruiz, bfroehle
2013-01-18 21:50:18ezio.melottisetmessageid: <>
2013-01-18 21:50:18ezio.melottilinkissue16997 messages
2013-01-18 21:50:18ezio.melotticreate