--- Adrian Howard <[EMAIL PROTECTED]> wrote: > You can, of course, use some kind of structured text in the test > description so you have output that looks something like: > > ok 1 - Test A/1/1 - fribble cleared > ok 2 - Test A/1/2 - bar set > ok 3 - Test A/1/3 - widget bobbling > ok 4 - Test A/2/1 - finkle barbed correctly > > and then parse it out with TAPx::Parser and friends. I believe a guy > from Yahoo did something similar - can't remember if the code ever > escaped though...
I don't recall seeing it on the CPAN, but as I recall, he was doing stuff like this: ok 1 - [gui][database] fribble cleared ok 2 - [database] - bar set ok 3 - [gui] - widget bobbling ok 4 - [gui][critical] - finkle barbed correctly And from that he wrote a custom harness with TAPx::Parser which could do stuff like check that all of the [gui] tests passed, all of the [database] tests passed, etc. This allowed him to effective tag and group sets of test results and potentially (my thought, though not mentioned in the discussion) take actions if tests with particular tags fail. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
