[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20693: SKIP not counted in TAP
From: |
Nick Bowler |
Subject: |
bug#20693: SKIP not counted in TAP |
Date: |
Fri, 29 May 2015 13:11:27 -0400 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On 2015-05-29 08:15 -0700, Arthur Schwarz wrote:
> skip causes the following issues:
> 1: It is not reported.
> 2: It is not summarized.
> 3: It must be subtracted from the plan (tests run), and
> 4: The .log file has TAP generated output and the test data intermixed.
>
> I think this is against the TAP definition?
In a way, because...
> skip
> ok
> PASS: test2.tap 1
> not ok
> FAIL: test2.tap 2
> 1..2
... it is your program's output that does not follow the specification.
There are two basic styles of skipping in TAP. You can skip a single
test result:
ok 1 # skip reason
or you can use the plan line to indicate that the entire test program is
to be skipped:
1..0 # skip reason
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)