- Original Message
From: Adam Kennedy <[EMAIL PROTECTED]>
> Without knowing anything that will specifically break, I think I'll take
> that bet. There's just too much code scattered around the place not to
> have SOMETHING break...
>
> Loser buys the winner a restaurant meal at the nex
On Tue, Sep 05, 2006 at 01:08:45 -0700, Ovid wrote:
> So who wants to bet against Adam and me?
I'm willing to bet that it'll take you at least a week to win, thus
making it seem like you actually lost ;-)
FWIW, pugs' test suite outputs diags to STDOUT. Things like
Test::TAP::Builder are much mor
On Tue, Sep 05, 2006 at 12:01:47 +0300, Yuval Kogman wrote:
> FWIW, pugs' test suite outputs diags to STDOUT. Things like
> Test::TAP::Builder are much more useful this way, too.
Err, i mean Test::TAP::Model.
--
Yuval Kogman <[EMAIL PROTECTED]>
http://nothingmuch.woobling.org 0xEBD27418
p
Ovid wrote:
Are there any Test:: modules which test the STDERR output directly or something
like that?
* Test::Output
* IO::Capture
There are tests that specifically check what's being sent to STDERR (as
well as STDOUT). Of course, these modules intercept STDOUT and STDERR
to keep them awa
> $ perl -MTest::Harness -wle 'runtests @ARGV' ~/tmp/stdout.t
> /Users/schwern/tmp/stdoutdubious
>Test returned status 1 (wstat 256, 0x100)
> DIED. FAILED test 1
>Failed 1/1 tests, 0.00% okay
> Failed Test Stat Wstat Total
Geoffrey Young wrote:
$ perl -MTest::Harness -wle 'runtests @ARGV' ~/tmp/stdout.t
/Users/schwern/tmp/stdoutdubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
Failed Test Stat
"t/sample-tests/todo" in the Test-Harness distribution reads:
<<<
print <>>
As one can see, the "1..5" plan is followed by the "todo 3 2;" directive.
This is supposed to indicate something about plan ahead todo tests. (Instead
of the "# TODO" directives in the individual tests'
