Documentation/dev-tools/testing-overview.rst

8 There are a number of different tools for testing the Linux kernel, so knowing
28 KUnit (Documentation/dev-tools/kunit/index.rst) is an entirely in-kernel system
44 Documentation/dev-tools/kunit/style.rst
47 kselftest (Documentation/dev-tools/kselftest.rst), on the other hand, is
69 The Linux Kernel supports two different code coverage measurement tools. These
74 Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
79 Documentation/dev-tools/kcov.rst is a feature which can be built in to the
88 The kernel also supports a number of dynamic analysis tools, which attempt to
94 Some of these tools are listed below:
97   Documentation/dev-tools/kmemleak.rst
99   use-after-free errors. See Documentation/dev-tools/kasan.rst
101   overflows. See Documentation/dev-tools/ubsan.rst
102 * KCSAN detects data races. See Documentation/dev-tools/kcsan.rst
104   KASAN and can be used in production. See Documentation/dev-tools/kfence.rst
112 These tools tend to test the kernel as a whole, and do not "pass" like
114 running tests on a kernel with these tools enabled: you can then be sure
117 Some of these tools integrate with KUnit or kselftest and will
124 directly (**at compile time**) using **static analysis** tools. The tools
131 examining the code. See the Documentation/dev-tools/sparse.rst documentation
147 Documentation/dev-tools/coccinelle.rst documentation page for details.
149 Beware, though, that static analysis tools suffer from **false positives**.