summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBagas Sanjaya <bagasdotme@gmail.com>2025-08-14 08:20:46 +0700
committerJonathan Corbet <corbet@lwn.net>2025-08-18 10:28:44 -0600
commitfea71fe1f060a722f7cb26aeca27d36d9370916d (patch)
tree33bc22bc2b94e1cef3cbc2e923aa0fdf3d1c349e
parent359ad700eb8b563461819b6227b021b280e37e3e (diff)
Documentation: ktap: Separate first bullet list items
The first bullet list items are shown in htmldocs output as combined with previous paragraph due to missing blank line separator. Add it. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> Reviewed-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250814012046.21235-3-bagasdotme@gmail.com
-rw-r--r--Documentation/dev-tools/ktap.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/dev-tools/ktap.rst b/Documentation/dev-tools/ktap.rst
index 54fac3d3bf7b..a9810bed5fd4 100644
--- a/Documentation/dev-tools/ktap.rst
+++ b/Documentation/dev-tools/ktap.rst
@@ -20,6 +20,7 @@ machine-readable, whereas the diagnostic data is unstructured and is there to
aid human debugging.
KTAP output is built from four different types of lines:
+
- Version lines
- Plan lines
- Test case result lines
@@ -38,6 +39,7 @@ All KTAP-formatted results begin with a "version line" which specifies which
version of the (K)TAP standard the result is compliant with.
For example:
+
- "KTAP version 1"
- "TAP version 13"
- "TAP version 14"
@@ -276,6 +278,7 @@ Example KTAP output
This output defines the following hierarchy:
A single test called "main_test", which fails, and has three subtests:
+
- "example_test_1", which passes, and has one subtest:
- "test_1", which passes, and outputs the diagnostic message "test_1: initializing test_1"