From: frowand.list@gmail.com
To: Frank Rowand <frowand.list@gmail.com>,
David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Tim.Bird@sony.com, Brendan Higgins <brendanhiggins@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
rmr167@gmail.com, guillaume.tucker@collabora.com,
dlatypov@google.com, kernelci@groups.io,
kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 2/2] ktap_v2: change "version 1" to "version 2" in examples
Date: Mon, 29 Aug 2022 18:31:50 -0500 [thread overview]
Message-ID: <20220829233150.3564612-3-frowand.list@gmail.com> (raw)
In-Reply-To: <20220829233150.3564612-1-frowand.list@gmail.com>
From: Frank Rowand <frank.rowand@sony.com>
Change the "version line" in example output from
"KTAP version 1" to "KTAP version 2".
Change version that should be used by compliant tests from 1 to 2.
Signed-off-by: Frank Rowand <frank.rowand@sony.com>
---
Changes since patch version 2:
- refresh version 2 patch 2/2 for new context
Documentation/dev-tools/ktap.rst | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/Documentation/dev-tools/ktap.rst b/Documentation/dev-tools/ktap.rst
index b9a57ceddd4f..ff77f4aaa6ef 100644
--- a/Documentation/dev-tools/ktap.rst
+++ b/Documentation/dev-tools/ktap.rst
@@ -39,6 +39,7 @@ version of the (K)TAP standard the result is compliant with.
For example:
- "KTAP version 1"
+- "KTAP version 2"
- "TAP version 13"
- "TAP version 14"
@@ -46,7 +47,7 @@ Note that, in KTAP, subtests also begin with a version line, which denotes the
start of the nested test results. This differs from TAP14, which uses a
separate "Subtest" line.
-While, going forward, "KTAP version 1" should be used by compliant tests, it
+While, going forward, "KTAP version 2" should be used by compliant tests, it
is expected that most parsers and other tooling will accept the other versions
listed here for compatibility with existing tests and frameworks.
@@ -202,9 +203,9 @@ An example of a test with two nested subtests:
::
- KTAP version 1
+ KTAP version 2
1..1
- KTAP version 1
+ KTAP version 2
1..2
ok 1 test_1
not ok 2 test_2
@@ -215,11 +216,11 @@ An example format with multiple levels of nested testing:
::
- KTAP version 1
+ KTAP version 2
1..2
- KTAP version 1
+ KTAP version 2
1..2
- KTAP version 1
+ KTAP version 2
1..2
not ok 1 test_1
ok 2 test_2
@@ -250,21 +251,21 @@ Example KTAP output
--------------------
::
- KTAP version 1
+ KTAP version 2
1..1
- KTAP version 1
+ KTAP version 2
1..3
- KTAP version 1
+ KTAP version 2
1..1
# test_1: initializing test_1
ok 1 test_1
ok 1 example_test_1
- KTAP version 1
+ KTAP version 2
1..2
ok 1 test_1 # SKIP test_1 skipped
ok 2 test_2
ok 2 example_test_2
- KTAP version 1
+ KTAP version 2
1..3
ok 1 test_1
# test_2: FAIL
--
Frank Rowand <frank.rowand@sony.com>
next prev parent reply other threads:[~2022-08-29 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:31 [PATCH v3 0/2] begin KTAP spec v2 process frowand.list
2022-08-29 23:31 ` [PATCH v3 1/2] ktap_v2: change version to 2-rc in KTAP specification frowand.list
2022-08-30 1:48 ` Bagas Sanjaya
2022-08-30 15:04 ` Frank Rowand
2022-08-30 12:54 ` Matthew Wilcox
2022-08-30 15:06 ` Frank Rowand
2022-08-29 23:31 ` frowand.list [this message]
2022-08-30 22:16 ` [PATCH v3 0/2] begin KTAP spec v2 process Frank Rowand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220829233150.3564612-3-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=guillaume.tucker@collabora.com \
--cc=keescook@chromium.org \
--cc=kernelci@groups.io \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmr167@gmail.com \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox