| /linux/lib/kunit/ |
| H A D | Kconfig | 2 # KUnit base configuration
6 tristate "KUnit - Enable support for unit tests"
9 Enables support for kernel unit tests (KUnit), a lightweight unit
19 bool "KUnit - Enable /sys/kernel/debug/kunit debugfs representation"
29 bool "Enable KUnit tests which print BUG stacktraces"
34 Enables fault handling tests for the KUnit framework. These tests may
40 tristate "KUnit test for KUnit" if !KUNIT_ALL_TESTS
43 Enables the unit tests for the KUnit test framework. These tests test
44 the KUnit test framework itself; the tests are both written using
45 KUnit and test KUnit. This option should only be enabled for testing
[all …]
|
| /linux/Documentation/translations/zh_TW/dev-tools/ |
| H A D | testing-overview.rst | 19 大多數內核測試都是用kselftest或KUnit框架之一編寫的。它們都讓運行測試
25 KUnit和kselftest的區別
34 KUnit（Documentation/dev-tools/kunit/index.rst）是用於“白箱”測
38 因此，KUnit測試最好針對內核中較小的、自包含的部分，以便能夠獨立地測
41 比如，一個KUnit測試可能測試一個單獨的內核功能（甚至通過一個函數測試
44 這也使得KUnit測試構建和運行非常地快，從而能夠作爲開發流程的一部分被
47 有關更詳細的介紹，請參閱KUnit測試代碼風格指南
58 中運行的測試，KUnit可能是更佳工具。
105 這些工具傾向於對內核進行整體測試，並且不像kselftest和KUnit一樣“傳遞”。
106 它們可以通過在啓用這些工具時運行內核測試以與kselftest或KUnit結合起來：
[all …]
|
| /linux/Documentation/translations/zh_CN/rust/ |
| H A D | testing.rst | 17 - KUnit 测试
21 KUnit 测试
24 这些测试来自 Rust 文档中的示例。它们会被转换为 KUnit 测试。
29 这些测试可以通过 KUnit 运行。例如，在命令行中使用 ``kunit_tool`` （ ``kunit.py`` ）::
33 或者，KUnit 也可以在内核启动时以内置方式运行。获取更多 KUnit 信息，请参阅
37 要使用这些 KUnit 文档测试，需要在内核配置中启用以下选项::
40 Kernel hacking -> Kernel Testing and Coverage -> KUnit - Enable support for unit tests
44 KUnit 测试即文档测试
66 然而，在内核中，这些测试会转换成 KUnit 测试套件。
69 通过与 KUnit 集成，Rust 的文档测试可以复用内核现有的测试设施。
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | architecture.rst | 4 KUnit Architecture
7 The KUnit architecture is divided into two parts:
15 The kernel testing library supports KUnit tests written in C using
16 KUnit. These KUnit tests are kernel code. KUnit performs the following
26 The test case is the fundamental unit in KUnit. KUnit test cases are organised
27 into suites. A KUnit test case is a function with type signature
34 Each KUnit test case receives a ``struct kunit`` context object that tracks a
35 running test. The KUnit assertion macros and other KUnit utilities use the
47 A KUnit suite includes a collection of test cases. The KUnit suites
72 with the KUnit test framework.
[all …]
|
| H A D | index.rst | 4 KUnit - Linux Kernel Unit Testing
26 KUnit (Kernel unit testing framework) provides a common framework for
27 unit tests within the Linux kernel. Using KUnit, you can define groups
29 if built-in, or load as a module. KUnit automatically flags and reports
35 KUnit tests are part of the kernel, written in the C (programming)
38 completion, KUnit can run around 100 tests in less than 10 seconds.
39 KUnit can test any kernel component, for example: file system, system
42 KUnit follows the white-box testing approach. The test has access to
43 internal system functionality. KUnit runs in kernel space and is not
46 In addition, KUnit has kunit_tool, a script (``tools/testing/kunit/kunit.py``)
[all …]
|
| H A D | run_manual.rst | 9 include KUnit in any kernel, read out results, and parse manually.
11 .. note:: KUnit is not designed for use in a production system. It is
18 KUnit tests can run without kunit_tool. This can be useful, if:
25 KUnit is configured with the ``CONFIG_KUNIT`` option, and individual
27 ``.config``. KUnit tests usually (but don't always) have config options
38 KUnit can be enabled or disabled at boot time, and this behavior is
61 KUnit can be accessed from userspace via the debugfs filesystem (See more
64 If ``CONFIG_KUNIT_DEBUGFS`` is enabled, the KUnit debugfs filesystem is
71 You can use debugfs to retrieve KUnit test results. The test results are
95 However, this feature is not available with KUnit suites that use init data,
[all …]
|
| H A D | start.rst | 7 This page contains an overview of the kunit_tool and KUnit framework,
9 and covers common problems users face when using KUnit for the first time.
13 KUnit has the same dependencies as the Linux kernel. As long as you can
14 build the kernel, you can run KUnit.
46 Configuring KUnit Kernel ...
47 Building KUnit Kernel ...
48 Starting KUnit Kernel ...
54 the ``Building KUnit Kernel`` step may take a while.
71 A good starting point for the ``.kunitconfig`` is the KUnit default config.
148 Running Tests without the KUnit Wrapper
[all …]
|
| /linux/Documentation/dev-tools/kunit/api/ |
| H A D | index.rst | 17 This page documents the KUnit kernel testing API. It is divided into the
20 Core KUnit API
29 - Documents the KUnit resource API
33 - Documents the KUnit Function Redirection API
35 Driver KUnit API
40 - Documents the KUnit clk API
44 - Documents the KUnit device tree (OF) API
48 - Documents the KUnit platform device API
|
| H A D | resource.rst | 7 This file documents the KUnit resource API.
18 Functions for using KUnit-managed struct device and struct device_driver.
|
| /linux/arch/riscv/kernel/tests/ |
| H A D | Kconfig.debug | 16 bool "KUnit test riscv module linking at runtime" if !KUNIT_ALL_TESTS
23 KUnit tests run during boot and output the results to the debug log
25 running the KUnit test harness, and not intended for inclusion into a
28 For more information on KUnit and unit tests in general please refer
29 to the KUnit documentation in Documentation/dev-tools/kunit/.
34 tristate "KUnit test for riscv kprobes" if !KUNIT_ALL_TESTS
|
| /linux/drivers/firmware/cirrus/ |
| H A D | Kconfig | 11 tristate "KUnit tests for Cirrus Logic cs_dsp" if !KUNIT_ALL_TESTS
16 This builds KUnit tests for cs_dsp.
17 For more information on KUnit and unit tests in general,
18 please refer to the KUnit documentation in
|
| /linux/net/mptcp/ |
| H A D | Kconfig | 26 tristate "This builds the MPTCP KUnit tests" if !KUNIT_ALL_TESTS
31 Only useful for kernel devs running KUnit test harness and are not
34 For more information on KUnit and unit tests in general please refer
35 to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/drivers/fpga/tests/ |
| H A D | Kconfig | 2 tristate "KUnit test for the FPGA subsystem" if !KUNIT_ALL_TESTS
8 For more information on KUnit and unit tests in general,
9 please refer to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/security/landlock/ |
| H A D | Kconfig | 30 bool "KUnit tests for Landlock" if !KUNIT_ALL_TESTS
35 Build KUnit tests for Landlock.
37 See the KUnit documentation in Documentation/dev-tools/kunit
39 Run all KUnit tests for Landlock with:
|
| /linux/drivers/base/test/ |
| H A D | Kconfig | 13 tristate "KUnit Tests for the device model" if !KUNIT_ALL_TESTS
18 tristate "KUnit Tests for property entry API" if !KUNIT_ALL_TESTS
23 tristate "KUnit Tests for software node fw_devlink links" if !KUNIT_ALL_TESTS
|
| /linux/fs/ext4/ |
| H A D | Kconfig | 78 tristate "KUnit tests for ext4" if !KUNIT_ALL_TESTS
82 This builds the ext4 KUnit tests.
84 KUnit tests run during boot and output the results to the debug log
86 running KUnit test harness and are not for inclusion into a production
89 For more information on KUnit and unit tests in general please refer
90 to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/sound/soc/ |
| H A D | Kconfig | 46 This option exists to facilitate running the KUnit tests for
47 the topology core, KUnit is frequently tested in virtual
50 to enable it if not doing a KUnit build.
53 tristate "KUnit tests for SoC topology"
70 tristate "KUnit tests for SoC card"
78 tristate "KUnit tests for SoC utils"
85 tristate "KUnit tests for SoC ops"
|
| /linux/Documentation/dev-tools/ |
| H A D | testing-overview.rst | 16 The bulk of kernel tests are written using either the kselftest or KUnit
22 parts of the kernel — then you'll want to use KUnit or kselftest.
25 The Difference Between KUnit and kselftest
28 KUnit (Documentation/dev-tools/kunit/index.rst) is an entirely in-kernel system
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
40 This also makes KUnit tests very fast to build and run, allowing them to be
43 There is a KUnit test style guide which may give further pointers in
58 kernel, however, KUnit may be the more appropriate tool.
113 kselftest or KUnit tests. They can be combined with KUnit or kselftest by
[all …]
|
| /linux/net/sunrpc/ |
| H A D | Kconfig | |
| /linux/security/apparmor/ |
| H A D | Kconfig | 120 tristate "Build KUnit tests for policy_unpack.c" if !KUNIT_ALL_TESTS
124 This builds the AppArmor KUnit tests.
126 KUnit tests run during boot and output the results to the debug log
128 running KUnit test harness and are not for inclusion into a
131 For more information on KUnit and unit tests in general please refer
132 to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/net/hsr/ |
| H A D | Kconfig | 45 tristate "PRP duplicate discard KUnit tests" if !KUNIT_ALL_TESTS
50 Only useful for kernel devs running KUnit test harness and are not
53 For more information on KUnit and unit tests in general please refer
54 to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/drivers/net/ethernet/microchip/vcap/ |
| H A D | Kconfig | 40 bool "KUnit test for VCAP library" if !KUNIT_ALL_TESTS
48 For more information on KUnit and unit tests in general, please refer
49 to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/drivers/net/ethernet/ibm/ |
| H A D | Kconfig | 31 bool "KUnit test for IBM LAN Virtual Ethernet support" if !KUNIT_ALL_TESTS
38 For more information on KUnit and unit tests in general, please refer
39 to the KUnit documentation in Documentation/dev-tools/kunit/.
|
| /linux/lib/ |
| H A D | Kconfig.debug | 2277 tristate "KUnit test for cpumask" if !KUNIT_ALL_TESTS
2283 For more information on KUnit and unit tests in general, please refer
2284 to the KUnit documentation in Documentation/dev-tools/kunit/.
2451 tristate "KUnit test printf() family of functions at runtime" if !KUNIT_ALL_TESTS
2460 tristate "KUnit test scanf() family of functions at runtime" if !KUNIT_ALL_TESTS
2469 tristate "KUnit test for seq_buf" if !KUNIT_ALL_TESTS
2478 tristate "KUnit test string functions at runtime" if !KUNIT_ALL_TESTS
2483 tristate "KUnit test string helpers at runtime" if !KUNIT_ALL_TESTS
2494 during the KUnit test run.
2499 tristate "KUnit test ffs-family functions at runtime" if !KUNIT_ALL_TESTS
[all …]
|
| /linux/drivers/of/ |
| H A D | Kconfig | 46 tristate "Devicetree KUnit Test" if !KUNIT_ALL_TESTS
50 This option builds KUnit unit tests for device tree infrastructure.
117 tristate "Device Tree overlay KUnit tests" if !KUNIT_ALL_TESTS
122 This option builds KUnit unit tests for the device tree overlay code.
|