Lines Matching +full:self +full:- +full:test

1 .. SPDX-License-Identifier: GPL-2.0
26 ------------------------------------------
28 KUnit (Documentation/dev-tools/kunit/index.rst) is an entirely in-kernel system
29 for "white box" testing: because test code is part of the kernel, it can access
32 KUnit tests therefore are best written against small, self-contained parts
36 For example, a KUnit test might test an individual kernel function (or even a
43 There is a KUnit test style guide which may give further pointers in
44 Documentation/dev-tools/kunit/style.rst
47 kselftest (Documentation/dev-tools/kselftest.rst), on the other hand, is
57 more information or functionality. If a test runs mostly or entirely within the
62 details. This aligns well with 'system' or 'end-to-end' testing.
70 can be used to verify that a test is executing particular functions or lines
72 and for finding corner-cases which are not covered by the appropriate test.
74 Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
75 used with the kernel to get global or per-module coverage. Unlike KCOV, it
76 does not record per-task coverage. Coverage data can be read from debugfs,
79 Documentation/dev-tools/kcov.rst is a feature which can be built in to the
80 kernel to allow capturing coverage on a per-task level. It's therefore useful
97   Documentation/dev-tools/kmemleak.rst
98 * KASAN detects invalid memory accesses such as out-of-bounds and
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
103 * KFENCE is a low-overhead detector of memory issues, which is much faster than
104   KASAN and can be used in production. See Documentation/dev-tools/kfence.rst
106   Documentation/locking/lockdep-design.rst
108   subsystem. See Documentation/trace/rv/runtime-verification.rst
112 These tools tend to test the kernel as a whole, and do not "pass" like
115 that none of these errors are occurring during the test.
129 Sparse can help test the kernel by performing type-checking, lock checking,
131 examining the code. See the Documentation/dev-tools/sparse.rst documentation
147 Documentation/dev-tools/coccinelle.rst documentation page for details.
153 -----------------------------
168 --------------------------------------
171 pre-processor so it's easier to check for bugs in macros using Coccinelle.