New submission from Antoine Pitrou:
It is sometimes useful to check for the log messages emitted by some piece of
code (especially a library). Would it be a good idea to add a dedicated
assertion method for that? I would propose the following API:
with self.assertLogging("logger.name", level="WARN") as cm:
...
The `cm` context manager could give access to all the log records and formatted
output lines for the given logger name (and children) and at least the given
logging level. I have something like that here, except not with a dedicated
assertion method:
https://bitbucket.org/optiflowsrd/obelus/src/c2a2f78068123264adde8cc3ece4889c61773f00/obelus/test/__init__.py?at=default#cl-20
----------
components: Library (Lib)
messages: 197022
nosy: ezio.melotti, michael.foord, pitrou, vinay.sajip
priority: normal
severity: normal
status: open
title: add unittest assertion for logging
type: enhancement
versions: Python 3.4
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue18937>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
