Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #81649 > unrolled thread

Logging with unittest

Started byJared Windover <jaredwindover@gmail.com>
First post2014-11-27 13:37 -0800
Last post2014-11-27 13:37 -0800
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python


Contents

  Logging with unittest Jared Windover <jaredwindover@gmail.com> - 2014-11-27 13:37 -0800

#81649 — Logging with unittest

FromJared Windover <jaredwindover@gmail.com>
Date2014-11-27 13:37 -0800
SubjectLogging with unittest
Message-ID<61a5d11a-716e-476c-9d17-d2703dcabba5@googlegroups.com>
I've been working with unittest for a while and just started using logging, and my question is: is it possible to use logging to display information about the tests you're running, but still have it be compatible with the --buffer option so that you only see it if a test fails? It seems like it would be a useful (and more standard than print statements) way to include stuff like parameter values near where a test may fail. 

What I currently have happening is that the logging output is shown regardless of whether or not the -b (or --buffer) flag is present. Any thoughts?

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web