On Jun 29, 2006, at 07:26, Michael Peters wrote:
This is a general problem with the way some of the testing modules work.
Only because they all use Test::Builder's output methods.
This doesn't resolve the problem of non-test modules emitting things to STDERR that could be useful when tracking down bugs, but what they might print is notTAP, so can't really be associated with particular tests.
I use Test::More::diag() (or main::diag()) for that. Best, David