b13fcb23d7
Currently, a bad logging call, e.g.
logger.info('oops', 'first', 2)
triggers the default logging handling, which is printing an error to
stderr but otherwise continuing.
For regular programs this behavior makes sense, a bad log message
shouldn't take down the program. But during tests, it is better not to
skip over such mistakes, but propagate them to the user.
|
||
|---|---|---|
| .. | ||
| test_fixture.py | ||
| test_formatter.py | ||
| test_reporting.py | ||