#2365 defect new
trial should completely manage its output stream
|Reported by:||glyph||Owned by:|
Description (last modified by glyph)
Right now warnings from tests and output from tests simply interrupt the reporter's reporting of success and failure, causing the output to not line up.
With the default reporter - whose output is not intended to be parsed - this is in principle simply aesthetic, but things (like buildbot) do actually parse. With other reporter plug-ins that emit structured output that is not newline-delimited though, random test output in the middle of the output stream would be even worse. (For example, an XML reporter where a test printed a '<'.)
There are related problems which are more technical. For example, trial knows to use untilConcludes but test cases aren't going to.
Trial should generally be aware of output from tests, and visually distinguish between stdout stderr so that warnings are clearly visible.
In the reporters packaged within trial, this should look something like this:
# verbose some.test.module SomeTestCase test_something ... [OUTPUT] """ a value was printed """ test_something ... [OK] =============================================================================== [OUTPUT] a value was printed some.test.module.SomeTestCase.test_something
# bwverbose some.test.module.SomeTestCase.test_something ... [OUTPUT] """ a value was printed """ some.test.module.SomeTestCase.test_something ... [OK]
Change History (19)
comment:8 Changed 9 years ago by glyph
- Keywords review added
- Owner changed from glyph to jml
- Priority changed from normal to highest
- Status changed from assigned to new