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 brett.cannon
Recipients brett.cannon
Date 2012-09-19.18:05:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348077938.27.0.260547344914.issue15974@psf.upfronthosting.co.za>
In-reply-to
Content
It would be nice to have something like sphinx's build output where the output is all kept on a single line except for failures.

The color would help when scrolling through current output looking for failures. Currently I just look until the failure count switches, but I can spot color more quickly and easily.

The reason for the compact output is that I simply don't typically care about passed tests, so why keep it visible? It also helps with noticing tests failures if those are the only tests that are kept in the terminal while the suite is running (obviously the output summary is still there).

This also suggests having an option to write out to a file the test results to make it easier to see the exact test execution order (and if passed tests are commented out then it's easier to pass the file to --fromfile to re-run the fail tests).
History
Date User Action Args
2012-09-19 18:05:38brett.cannonsetrecipients: + brett.cannon
2012-09-19 18:05:38brett.cannonsetmessageid: <1348077938.27.0.260547344914.issue15974@psf.upfronthosting.co.za>
2012-09-19 18:05:37brett.cannonlinkissue15974 messages
2012-09-19 18:05:37brett.cannoncreate