selftest should print errors as they occur
Bug #408192 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Martin Pool | ||
Bug Description
At the moment bzr selftest prints just a short message for failures as they occur, and then prints the full error when the test run completes. I don't think there's any good reason for this except perhaps that it may be the same as the standard Python test runner, and it causes a needless delay before you can start investigating the failure, and means you don't see any details at all if the run is interrupted (bug 140858).
selftest --subunit can be used as a kind of workaround because it does stream out the results.
| description: | updated |
Revision history for this message
| Martin Packman (gz) wrote | #1 |
| tags: | added: selftest |
Revision history for this message
| Martin Pool (mbp) wrote | #2 |
Revision history for this message
| Martin Pool (mbp) wrote | #3 |
| Changed in bzr: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
The behaviour requested here is now what actually happens since it was accidentally changed when testtools was introduced.
However, as my most frequent use of selftest is not running the whole suite with an occasional single error I want to investigate right then, but running a small set of tests I expect to be failing until I get them to pass, having it print several screenfulls of text twice is obnoxious. So, bug 625597 is asking for the old behaviour back, and I'd much prefer fixing that and bug 140858 (which appears to also be fixed already?) and wontfixing this.