dev-tools/kunit/style.rst

24 suite is a group of tests which test a related area of the kernel. A subsystem
25 is a set of test suites which test different parts of a kernel subsystem
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 test subsystem should match a single kernel module. If the code being tested
34 cannot be compiled as a module, in many cases the subsystem should correspond to
42 If a test subsystem name has multiple components, they should be separated by
43 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
64   suffix. ``qos`` is also ambiguous as a subsystem name, because several parts
65   of the kernel have a ``qos`` subsystem. ``power_qos`` would be a better name.
67   The corresponding module name is ``parport_pc``, so this subsystem should also
84 Test suites are named after the subsystem they are part of. If a subsystem
86 subsystem name, separated by an underscore.
89 subsystem (for example, both unit tests and integration tests), they should be
94 The full test suite name (including the subsystem name) should be specified as
99   Part of the ``ext4`` subsystem, testing the ``inode`` area.
103   Part of the ``apparmor`` subsystem, testing the ``property_entry`` area.
105   The ``kasan`` subsystem has only one suite, so the suite name is the same as
106   the subsystem name.
111   There is no reason to state the subsystem twice.
113   The suite name is ambiguous without the subsystem name.
115   Because there is only one suite in the ``kasan`` subsystem, the suite should
161 * be listed either alongside the config entries for the driver/subsystem being