Mikeal Rogers wrote: > QA has written an entirely new test framework and new logger for > chandler testing. We also have a variety of new features. Some of the > new features require your input as to what sane defaults should be when > running chandler tests.
I didn't completely understand how each of the levels and masking etc.
works, but my preference is to have really minimal output by default.
Following Python unittest output I like having just a dot (.) for a
passed test (or in some cases testname + "ok" on a line). I need to
think about this a little more...
In case an error occurs, outputting everything I need or is available:
location of error, why the error happened ("expected x, got y"),
backtrace, ...
--
Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
