Skip Menu |

This queue is for tickets about the TAP-Parser CPAN distribution.

Report information
The Basics
Id: 28526
Status: resolved
Priority: 0/
Queue: TAP-Parser

People
Owner: Nobody in particular
Requestors: EWILHELM [...] cpan.org
Cc: tapx-dev [...] hexten.net
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



CC: "TAP::Parser Developers" <tapx-dev [...] hexten.net>
Subject: odd todo/skip results running TAP::Parser tests under runtests
Has anyone run the tests with runtests lately? It seems like we should have a scheme for doing that somehow. I'm a bit confused by the results here though. Should we be printing "TODO PASSED" and "SKIPPED" there? $ runtests t/020-regression.t t/020-regression......2268/0 # - # fnurk: skib # ponk: gleeb # - # bar: krup # foo: plink # ... # t/020-regression......2296/0 # expected: # - 1 # - 2 # - 4 # got: # - 1 # - pong # - 4 # ... # t/020-regression...... All 3289 subtests passed (less 1 skipped subtest: 3288 okay) (1 TODO test unexpectedly succeeded) Test Summary Report ------------------- t/020-regression.t (Wstat: 0 Tests: 3289 Failed: 0) TODO passed: 1159 Tests skipped: 1172 Files=1, Tests=3289, 4 wallclock secs ( 1.56 cusr + 0.26 csys = 1.82 CPU) --Eric
Fixed - and we're now regularly running our tests with the version of T::P under test using perl -Ilib bin/runtests -b