[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20716: TAP Protocol skip is not recognized.
From: |
Arthur Schwarz |
Subject: |
bug#20716: TAP Protocol skip is not recognized. |
Date: |
Mon, 1 Jun 2015 15:07:41 -0700 |
http://testanything.org/
DIRECTIVES
Directives are special notes that follow a # on the test line. Only two are
currently defined: TODO and SKIP. Note that these two keywords are not
case-sensitive.
The tap-driver.sh does accept 'ok # skip' but requires 'ok # SKIP'. The TAP
standard says that skip is not case sensitive (it is case insensitive?).
It is reported as XPASS (because TAP_LOG_DRIVER_FLAGS = --expect-failure
yes) but a test-plan of 1..0 is reported as SKIP. This seems inconsistent.
If I have
1..1
ok # SKIP
Is reported as
XPASS: test2.tap 1
=================================
Testsuite summary for test 0.5
=================================
# TOTAL: 1
# PASS: 0
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 1
# ERROR: 0
=================================
See src/test-suite.log
================================
test2.trs
:global-test-result: FAIL
:recheck: yes
:copy-in-global-log: yes
:test-result: XPASS
while
1..0
Is reported as
SKIP: test2.tap
=================================
Testsuite summary for test 0.5
=================================
# TOTAL: 1
# PASS: 0
# SKIP: 1
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
=================================
Test2.tap
:global-test-result: SKIP
:recheck: no
:copy-in-global-log: yes
:test-result: SKIP
And what is also interesting is that the output is also different. No
test-suite.log file (seems ok except I would expect some indication) and,
since this is the TAP protocol, I would expect that Diagnostics would be
captured in a test-suite.log as is indicated in the ':copy-in-global-log:'
yes metadata tag.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#20716: TAP Protocol skip is not recognized.,
Arthur Schwarz <=