On Tue, Sep 26, 2006 at 06:15:15PM -0400, David Golden wrote:
> On 9/26/06, Tim Bunce <[EMAIL PROTECTED]> wrote:
>
> > Or do I need to prioritize getting some sort of output capture even
> > in the case of test.pl? In this case, since t/*.t is run as well,
> > the Test::Harness "All tests successful" line would get picked up
> > and the the results of test.pl would be ignored.
>
> That seems like the best approach. Make won't run test.pl is any of the
> t/*.t tests failed. So if you know that none failed but make failed
> then you'll know it was test.pl that failed.
>
> It's still tricky. If I tee to both show the output to the user
> and collect the output, then I can parse for Test::Harness
> success/failure messages, but the actual exit code of test.pl is
> ignored.
Is the 'actual exit code of test.pl' important? (Beyond simple
success vs failure.)
If you're parsing for Test::Harness success/failure messages couldn't
you also parse for success/failure message from make:
(make test || echo "make test failed: $?") | tee ...
Tim.
