Given the following TAP, Smolder says my test was 50% successful, when it should only be 33.33% successful:
not ok 2
This isn't really so much of a Smolder problem as a TAP interpretation problem. Does your example mean 1 of 2 tests failed and you gave a bad plan? Or does it mean that your plan was right but you didn't actually follow it?
I'll post the TAP list to see what the consensus is for that and then change (or not) Smolder accordingly.
The plan is actually correct - there were 3 tests that were supposed to be run; test 3 wasn't run, in this case because test 2's failure caused the test to die.
Also, prove treats the unrun test as failed, as well:
$ (echo '1..2'; echo 'ok 1') | prove -v --exec='cat -' /dev/null
Failed 1/2 subtests
Test Summary Report
/dev/null (Wstat: 0 Tests: 1 Failed: 0)
Parse errors: Bad plan. You planned 2 tests but ran 1.
Files=1, Tests=1, 0 wallclock secs ( 0.03 usr + 0.01 sys = 0.04 CPU)
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.