On Oct 26, 2006, at 9:37 AM, Paul Beckingham wrote:
> and waiting for the test output/TAP to be parsed takes quite a
while.
> Just my $0.02 worth.
> -=Chris
To each his own, but my thoughts were not that it takes time to
parse, or that there is any unreasonable performance issue here -
just that it is so completely *unnecessary* to say "ok" lots of times.
It's only unnecessary if the test program doesn't crash! Compare
ease of debugging for these two cases:
1..10_000_000 sparse
*segfault*
vs.
1..10_000_000
ok 1 - use_ok Foo::Bar
ok 2 - input = 0
ok 3 - input = 1
[... snip ...]
ok 999999 - input = 999997
ok 1000000 - input = 999998
ok 1000001 - input = 999999
*segfault*
In the former case, perhaps all 10_000_000 tests passed and the test
program failed in END{}, or perhaps it died on the first test. You
just don't know without re-running the tests in a debugger, or
turning off sparse.
In the latter case, the harness can tell you how far along you were
before the tests failed. If the harness is smart enough to report
the last test result before the crash, you can even guess that "input
= 1000000" caused the crash.
In even scarier terms, would you prefer to see an RT or smoke report
about your module with the former or the latter detail?
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
Clotho Advanced Media, Inc. - Creators of MediaLandscape Software
(http://www.media-landscape.com/) and partners in the revolutionary
Croquet project (http://www.opencroquet.org/)
--
Chris Dolan, Software Developer, http://www.chrisdolan.net/
Public key: http://www.chrisdolan.net/public.key
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
