Lines Matching full:should

33 rule of thumb is that a test subsystem should match a single kernel module. If
35 should correspond to a directory in the source tree or an entry in the
39 Test subsystems should be named after the code being tested, either after the
41 subsystems should be named to avoid ambiguity where necessary.
43 If a test subsystem name has multiple components, they should be separated by
62   Names should use underscores, not dashes, to separate words. Prefer
65   As well as using underscores, this name should not have "kunit-test" as a
69   The corresponding module name is ``parport_pc``, so this subsystem should also
87 contains several suites, the specific area under test should be appended to the
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
119   Because there is only one suite in the ``kasan`` subsystem, the suite should
121   ``integration_test``. Should a separate test suite with, for example, unit
131 Tests should be named after what they're testing. This is often the name of the
133 As tests are C functions, they should be named and written in accordance with
151 Should it be necessary to refer to a test outside the context of its test suite,
152 the *fully-qualified* name of a test should be the suite name followed by the
158 Every test suite should be tied to a Kconfig entry.
172 a module), Kconfig entries for tests should be tristate.
194 KUnit tests can often be compiled as a module. These modules should be named
199 ``<suite>_test.c`` (or, as above, ``<suite>_kunit.c``). This file should be