--- Andy Armstrong <[EMAIL PROTECTED]> wrote: > I like it. At some point in the future we could spew that information > out as part of the TAP stream (as YAMLish metadata) and gather and > analyse it in the harness.
Sounds great, but that we consume the test data, not produce it. The reason I was thinking about a Test::More wrapper is that this could ensure that the code picks it up. Oh, duh. When we run the perl process, internally we could do something like: perl -Isome/lib -MCapture::Inc t/test_prog.t That could work. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
