On 03/06/2012 05:29 PM, Hyrum K Wright wrote: > After a bit of a bump today, I've added the use of the python logging > module to our test suite as a way of logging output from the test > framework and the tests themselves. The end goal is to remove all the > many print() calls we have in the tests, and run almost everything > through the logger, allowing us to better control where the log gets > sent to, its formatting, etc. > > I'm sure I'll break more things along the way, and I've yet to fully > iron out the standards for using INFO vs. WARN vs. ERROR within the > tests, but I'd appreciate any insight or help or questions folks might > have as this transition goes forward.
+1. One subgoal I would have for such a conversion is that --quiet runs actually be quiet, printing *only* the FAIL: or XPASS: summary lines (not, say, every stack trace behind every XFAIL: test such as happens today). -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
