On Fri, 2005-07-29 at 02:49 +0100, Adrian Howard wrote: > I've been pondering custom test runners recently and have hit the > familiar problem of Test::Harness::Straps not capturing STDERR, so > missing the diagnostics that Test::Builder outputs.
> Is there a better way I'm missing? If you can use your own test harness, use Test::Harness::Straps::analyze() or Test::Harness::Straps::analyze_fh() to collect STDERR and STDOUT from the tested process. -- c