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 fperez
Recipients Yaroslav.Halchenko, brian.curtin, exarkun, fperez, michael.foord, pitrou
Date 2010-04-09.21:19:49
SpamBayes Score 1.9703694e-09
Marked as misclassified No
Message-id <1270847991.24.0.339680255809.issue7897@psf.upfronthosting.co.za>
In-reply-to
Content
Yarick: Yes, I do actually see the value of the summary view.  When I have a parametric test that fails, I tend to just run nose with -x so it stops at the first error and with the --pdb options to study it, so I simply ignore all the other failures.  To me, test failures are quite often like compiler error messages: if there's a lot of them, it's best to look only at the first few, fix those and try again, because the rest could be coming from the same cause.

I don't know if Michael has plans/bandwidth to add the summary support as well, but I agree it would be very nice to have, just not at the expense of individual reporting.
History
Date User Action Args
2010-04-09 21:19:51fperezsetrecipients: + fperez, exarkun, pitrou, michael.foord, brian.curtin, Yaroslav.Halchenko
2010-04-09 21:19:51fperezsetmessageid: <1270847991.24.0.339680255809.issue7897@psf.upfronthosting.co.za>
2010-04-09 21:19:49fperezlinkissue7897 messages
2010-04-09 21:19:49fperezcreate