summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMuhammad Usama Anjum <usama.anjum@collabora.com>2024-06-12 09:27:23 +0200
committerShuah Khan <skhan@linuxfoundation.org>2024-07-11 19:23:54 +0200
commitb00db6fd2a301c5057d63c19d596818845c9a603 (patch)
tree5c5f466d4d8002bb849d1c21cbd4a0824c16b782
parentselftests/resctrl: Remove test name comparing from write_bm_pid_to_resctrl() (diff)
downloadlinux-b00db6fd2a301c5057d63c19d596818845c9a603.tar.xz
linux-b00db6fd2a301c5057d63c19d596818845c9a603.zip
selftests: Add information about TAP conformance in tests
Although "TAP" word is being used already in documentation, but it hasn't been defined in informative way for developers that how to write TAP conformant tests and what are the benefits. Write a short brief about it. Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
-rw-r--r--Documentation/dev-tools/kselftest.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/dev-tools/kselftest.rst b/Documentation/dev-tools/kselftest.rst
index dcf634e411bd..f3766e326d1e 100644
--- a/Documentation/dev-tools/kselftest.rst
+++ b/Documentation/dev-tools/kselftest.rst
@@ -228,6 +228,13 @@ In general, the rules for selftests are
* Don't cause the top-level "make run_tests" to fail if your feature is
unconfigured.
+ * The output of tests must conform to the TAP standard to ensure high
+ testing quality and to capture failures/errors with specific details.
+ The kselftest.h and kselftest_harness.h headers provide wrappers for
+ outputting test results. These wrappers should be used for pass,
+ fail, exit, and skip messages. CI systems can easily parse TAP output
+ messages to detect test results.
+
Contributing new tests (details)
================================