--- Sam Vilain <[EMAIL PROTECTED]> wrote: > Actually a large part of my > initial reaction was due to the use of the word "concatenation". > Looking at the module documentation I see that it's not anywhere near > as simplistic as that.
Yes, I did oversimplify the description. I can see how that could be confusing. > However the usual problematic boundary between the harness and the > test > is there. How do you solve this for Test::Aggregate, is it by making > it one test at the TAP level for each aggregated test? No, we let all of the tests run in sequence. To really understand it, run the Test::Aggregate tests. I automatically generate a file named 'dump.t' and that's essentially what gets run. You can open that up to see my approach. To be fair, I'm not overly keen on my approach, but it had the beauty of "minimal magic" and it works well. 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/
