dev-tools/kunit/style.rst

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
38 Test subsystems should be named after the code being tested, either after the
40 subsystems should be named to avoid ambiguity where necessary.
42 If a test subsystem name has multiple components, they should be separated by
60   Names should use underscores, not dashes, to separate words. Prefer
63   This name should use underscores, and not have "kunit-test" as a
67   The corresponding module name is ``parport_pc``, so this subsystem should also
85 contains several suites, the specific area under test should be appended to the
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
115   Because there is only one suite in the ``kasan`` subsystem, the suite should
117   ``integration_test``. It should be a separate test suite. For example, if the
128 Tests should be named after what they are testing. This is often the name of the
130 As tests are C functions, they should be named and written in accordance with
148 Should it be necessary to refer to a test outside the context of its test suite,
149 the *fully-qualified* name of a test should be the suite name followed by the
155 Every test suite should be tied to a Kconfig entry.
169 be built as a module), Kconfig entries for tests should be tristate.
192 with regular modules, KUnit modules should be named after the test suite,
206 ``tests/<suite>_kunit.c``. The ``tests`` directory should be placed at