Lines Matching full:test
4 Test Style and Nomenclature
24 and subsystems. A test suite is a group of tests which test a related area of
25 the kernel, and a subsystem is a set of test suites which test different parts
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
32 or more KUnit test suites which test the same driver or part of the kernel. A
33 rule of thumb is that a test subsystem should match a single kernel module. If
39 Test subsystems should be named after the code being tested, either after the
40 module (wherever possible), or after the directory or files being tested. Test
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
64 ``qos-kunit-test``
65 As well as using underscores, this name should not have "kunit-test" as a
74 simply a way of categorising test suites and naming modules which
81 KUnit tests are grouped into test suites, which cover a specific area of
82 functionality being tested. Test suites can have shared initialisation and
84 Not all subsystems will need to be split into multiple test suites (e.g. simple drivers).
86 Test suites are named after the subsystem they are part of. If a subsystem
87 contains several suites, the specific area under test should be appended to the
90 In the event that there are multiple types of test using KUnit within a
92 separate suites, with the type of test as the last element in the suite name.
96 The full test suite name (including the subsystem name) should be specified as
100 Example test suites could include:
121 ``integration_test``. Should a separate test suite with, for example, unit
124 Test Cases
128 codepath, property, or function. In the test output, individual tests' results
139 naming. It's a good idea to make your test functions `static` to avoid
142 Example test names include:
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
153 test name, separated by a colon (i.e. ``suite:test``).
155 Test Kconfig Entries
158 Every test suite should be tied to a Kconfig entry.
162 * be named ``CONFIG_<name>_KUNIT_TEST``: where <name> is the name of the test
171 Unless there's a specific reason not to (e.g. the test is unable to be built as
179 tristate "KUnit test for foo" if !KUNIT_ALL_TESTS
191 Test File and Module Names
195 after the test suite, followed by ``_test``. If this is likely to conflict with
198 The easiest way of achieving this is to name the file containing the test suite
200 placed next to the code under test.
202 If the suite name contains some or all of the name of the test's parent