Adrian Howard wrote:
> Maybe use the levels from Log4J, Log::Log4perl, et al?
> 
> fatal
> error
> warn
> info
> debug

Ok, maybe take that and tailor it more to testing.  Here it is in order of
severity.  The recommended display level would be "warn".

fatal !!!!!!!

There's an error in the TAP producer and it has to shut down.  Test::More's
"WHOA THERE!" messages are another.

fail !!!!!!

Info about a test which failed.  This would be all existing failure
diagnostics, the "Bail out!" message and end of failing test script messages
like "You ran 3 but said you'd run 5".

warn !!!!!

There's an ambiguity in the use of the TAP producer.  Test::More's messages
like "you named a test with a number, confusing".

notice !!!!

"Normal but significant condition" (from syslog).  This is some text you want
the user to see that isn't associated with a particular test.  "Trying to
connect to the Internet".  "The next test might take a long time".

pass !!!

Info about a test which passed.

info !!

General information about the test that the user probably doesn't need to see.
 This is currently done with a "# foo" comment sent to STDOUT.

debug !

Debugging information.

Reply via email to