5 The kernel contains a set of "self tests" under the tools/testing/selftests/
6 directory. These are intended to be small tests to exercise individual code
7 paths in the kernel. Tests are intended to be run after building, installing
10 On some systems, hot-plug tests could hang forever waiting for cpu and
11 memory to be ready to be offlined. A special hot-plug target is created
12 to run full range of hot-plug tests. In default mode, hot-plug tests run
13 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
14 run on a single cpu as opposed to all hotplug capable cpus, and memory
15 hotplug test is run on 2% of hotplug capable memory instead of 10%.
17 Running the selftests (hotplug tests are run in limited mode)
18 =============================================================
22 $ make -C tools/testing/selftests
26 $ make -C tools/testing/selftests run_tests
28 To build and run the tests with a single command, use::
32 Note that some tests will require root privileges.
34 Build and run from user specific object directory (make O=dir)::
36 $ make O=/tmp/kselftest kselftest
38 Build and run KBUILD_OUTPUT directory (make KBUILD_OUTPUT=)::
40 $ make KBUILD_OUTPUT=/tmp/kselftest kselftest
42 The above commands run the tests and print pass/fail summary to make it
43 easier to understand the test results. Please find the detailed individual
44 test results for each test in /tmp/testname file(s).
46 Running a subset of selftests
47 =============================
49 You can use the "TARGETS" variable on the make command line to specify
50 single test to run, or a list of tests to run.
52 To run only tests targeted for a single subsystem::
54 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
56 You can specify multiple tests to build and run::
58 $ make TARGETS="size timers" kselftest
60 Build and run from user specific object directory (make O=dir)::
62 $ make O=/tmp/kselftest TARGETS="size timers" kselftest
64 Build and run KBUILD_OUTPUT directory (make KBUILD_OUTPUT=)::
66 $ make KBUILD_OUTPUT=/tmp/kselftest TARGETS="size timers" kselftest
68 The above commands run the tests and print pass/fail summary to make it
69 easier to understand the test results. Please find the detailed individual
70 test results for each test in /tmp/testname file(s).
72 See the top-level tools/testing/selftests/Makefile for the list of all
75 Running the full range hotplug selftests
76 ========================================
78 To build the hotplug tests::
80 $ make -C tools/testing/selftests hotplug
82 To run the hotplug tests::
84 $ make -C tools/testing/selftests run_hotplug
86 Note that some tests will require root privileges.
92 You can use kselftest_install.sh tool installs selftests in default
93 location which is tools/testing/selftests/kselftest or a user specified
96 To install selftests in default location::
98 $ cd tools/testing/selftests
99 $ ./kselftest_install.sh
101 To install selftests in a user specified location::
103 $ cd tools/testing/selftests
104 $ ./kselftest_install.sh install_dir
106 Running installed selftests
107 ===========================
109 Kselftest install as well as the Kselftest tarball provide a script
110 named "run_kselftest.sh" to run the tests.
112 You can simply do the following to run the installed Kselftests. Please
113 note some tests will require root privileges::
118 Contributing new tests
119 ======================
121 In general, the rules for selftests are
123 * Do as much as you can if you're not root;
125 * Don't take too long;
127 * Don't break the build on any architecture, and
129 * Don't cause the top-level "make run_tests" to fail if your feature is
132 Contributing new tests (details)
133 ================================
135 * Use TEST_GEN_XXX if such binaries or files are generated during
138 TEST_PROGS, TEST_GEN_PROGS mean it is the executable tested by
141 TEST_CUSTOM_PROGS should be used by tests that require custom build
142 rule and prevent common build rule use.
144 TEST_PROGS are for test shell scripts. Please ensure shell script has
145 its exec bit set. Otherwise, lib.mk run_tests will generate a warning.
147 TEST_CUSTOM_PROGS and TEST_PROGS will be run by common run_tests.
149 TEST_PROGS_EXTENDED, TEST_GEN_PROGS_EXTENDED mean it is the
150 executable which is not tested by default.
151 TEST_FILES, TEST_GEN_FILES mean it is the file which is used by
157 The kselftest_harness.h file contains useful helpers to build tests. The tests
158 from tools/testing/selftests/seccomp/seccomp_bpf.c can be used as example.
163 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
170 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
171 :functions: TH_LOG TEST TEST_SIGNAL FIXTURE FIXTURE_DATA FIXTURE_SETUP
172 FIXTURE_TEARDOWN TEST_F TEST_HARNESS_MAIN
177 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
180 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
181 :functions: ASSERT_EQ ASSERT_NE ASSERT_LT ASSERT_LE ASSERT_GT ASSERT_GE
182 ASSERT_NULL ASSERT_TRUE ASSERT_NULL ASSERT_TRUE ASSERT_FALSE
183 ASSERT_STREQ ASSERT_STRNE EXPECT_EQ EXPECT_NE EXPECT_LT
184 EXPECT_LE EXPECT_GT EXPECT_GE EXPECT_NULL EXPECT_TRUE
185 EXPECT_FALSE EXPECT_STREQ EXPECT_STRNE