Re: Reporting 'missing' tests as failed in Test::Harness

2007-01-06 Thread Michael G Schwern
Ovid wrote: > Summary: if your TAP suddenly jumps from test #2 to test #29, > Test::Harness reports that tests #3 through #28 have 'failed'. > > TAPx::Harness does not report them as failures, but as parse errors > (because it's bad TAP). Is a 'parse error' a reasonable compromise? Technicall

Reporting 'missing' tests as failed in Test::Harness

2007-01-06 Thread Ovid
Summary: if your TAP suddenly jumps from test #2 to test #29, Test::Harness reports that tests #3 through #28 have 'failed'. TAPx::Harness does not report them as failures, but as parse errors (because it's bad TAP). Is a 'parse error' a reasonable compromise? More information below, if you'r