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 pitrou
Recipients Julian, Yaroslav.Halchenko, abingham, bfroehle, borja.ruiz, brett.cannon, 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-19.19:28:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358623525.3619.5.camel@localhost.localdomain>
In-reply-to <>
> I think we're going to have to separate out two counts in the metrics
> - the total number of tests (the current counts), and the total number
> of subtests (the executed subtest blocks).

This is a reasonable proposal. On the other hand, it was already the
case that a single test could count for several failures (for example,
an exception in the test method and another in tearDown). Therefore, I
think it is independent from the subtest proposal and could be tackled
separately (which would also help keep this issue focussed :-)).
Date User Action Args
2013-01-19 19:28:05pitrousetrecipients: + pitrou, brett.cannon, spiv, exarkun, ncoghlan, ezio.melotti, 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-19 19:28:05pitroulinkissue16997 messages
2013-01-19 19:28:03pitroucreate