Lines Matching full:subsystem

25 the kernel, and a subsystem is a set of test suites which test different parts
26 of the same kernel subsystem or driver.
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
33 rule of thumb is that a test subsystem should match a single kernel module. If
34 the code being tested can't be compiled as a module, in many cases the subsystem
43 If a test subsystem name has multiple components, they should be separated by
44 underscores. *Do not* include "test" or "kunit" directly in the subsystem name
66   suffix, and ``qos`` is ambiguous as a subsystem name. ``power_qos`` would be a
69   The corresponding module name is ``parport_pc``, so this subsystem should also
86 Test suites are named after the subsystem they are part of. If a subsystem
88 subsystem name, separated by an underscore.
91 subsystem (e.g., both unit tests and integration tests), they should be put into
96 The full test suite name (including the subsystem name) should be specified as
103   Part of the ``ext4`` subsystem, testing the ``inode`` area.
107   Part of the ``apparmor`` subsystem, testing the ``property_entry`` area.
109   The ``kasan`` subsystem has only one suite, so the suite name is the same as
110   the subsystem name.
115   There's no reason to state the subsystem twice.
117   The suite name is ambiguous without the subsystem name.
119   Because there is only one suite in the ``kasan`` subsystem, the suite should
164 * be listed either alongside the config entries for the driver/subsystem being