Inconsistent suppression of traceback in skipping test
Bug #1518101 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| testtools |
Fix Released
|
Medium
|
Jonathan Lange | ||
Bug Description
We currently suppress traceback for tests that raise TestSkipped (hardcoded). However, we also allow parametrization of the exception that indicates whether a test is being skipped (TestCase.
If you change that to another exception, say unittest.SkipTest, tests will be skipped, but tracebacks will be included in the output, which is not what I want, nor what I expect most people would want.
Revision history for this message
| Jonathan Lange (jml) wrote | #1 |
Revision history for this message
| Jonathan Lange (jml) wrote | #2 |
| Changed in testtools: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Jonathan Lange (jml) wrote | #3 |
| Changed in testtools: | |
| assignee: | nobody → Jonathan Lange (jml) |
| status: | Triaged → Fix Committed |
| milestone: | none → next |
| Changed in testtools: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
unittest.SkipTest is needed because of https:/