--- you can reply above this line --- New issue 112: A way to report failures as soon as they occur, not afterwards http://bitbucket.org/hpk42/py-trunk/issue/112/a-way-to-report-failures-as-soon-as-they-occur-not
Anonymous on Tue, 20 Jul 2010 09:59:55 +0200: Description: Now all tests are run and failures reported afterwards, so for a huge test suite, you can't start fixing the first failures, nor you know that this is a critical failure and just stop the test run. It would be nice if you could pass some parameter and get reports interleaved with test runs. It's not the same as "stop on first failure", because tests should keep on running even after reporting a failed test. -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue. _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
