Adrian Howard wrote: > > On 5 Oct 2006, at 15:11, Paul Beckingham wrote: > >> Recently I was required to create another flavor of test harness that >> runs tests, then captures and stores output. >> >> The nature of my testing means that I am running millions of tests, >> and the resultant captured output is therefore huge. So I modified my >> tests to do the *equivalent* of the following: > [snip] > > Personally I would say it would be better to leave the things generating > the TAP output alone, and have the test harness only store the test > failures. Ovid's TAPx::Parser makes this pretty darn easy, and it's not > stupidly difficult with Test::Harness::Straps although it needs some > sneakyness with private methods.
I'm with Adrian. Printing out "ok" 100,000 times shouldn't be a big deal unless you're reading the TAP via some sort of IP over clay tablets protocol. But... Test::Builder does store the test history and this can get prohibitive. There is a wishlist item for this and will gladly accept a patch. I originally intended this for Test::AtRuntime which can produce an infinite stream of TAP. http://rt.cpan.org/Public/Bug/Display.html?id=8387 Something like: $tb->no_history(1); with the caveat that this makes summary() and details() no longer work.
