On Fri, 6 Feb 2004 13:34:01 -0800, Michael G Schwern wrote:
Test::Harness parses 'ok' and 'not ok' and 'Bail out'... Test::*
modules produce the output Test::Harness parses. So your extra logic
to parse depends on would go into your Test::Harness extension, but
the depends_on() function to
On Fri, Feb 06, 2004 at 11:03:42AM -0600, Scott Bolte wrote:
I'd like to propose an addition to the Test::Harness parsing
rules to support dependency analysis. That, in turn, allows
monitoring for file changes and selective, immediate
re-execution of test files. Is
On Sun, Feb 08, 2004 at 08:41:59AM -0600, Scott Bolte ([EMAIL PROTECTED]) wrote:
I agree, but I still believe it would be good if Test::Harness
laid out syntax rules for extensions.
There are no extensions. They're up to whoever wants to. I'm certainly
not going to define
On Sun, Feb 08, 2004 at 05:27:02PM -0600, Andy Lester wrote:
On Sun, Feb 08, 2004 at 08:41:59AM -0600, Scott Bolte ([EMAIL PROTECTED]) wrote:
I agree, but I still believe it would be good if Test::Harness
laid out syntax rules for extensions.
There are no extensions. They're up to
On Sun, 8 Feb 2004 17:27:02 -0600, Andy Lester wrote:
On Sun, Feb 08, 2004 at 08:41:59AM -0600, Scott Bolte ([EMAIL PROTECTED]
) wrote:
I agree, but I still believe it would be good if Test::Harness
laid out syntax rules for extensions.
There are no extensions. They're up to
