Lines Matching full:suite

24 suite is a group of tests which test a related area of the kernel. A subsystem
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
81 shutdown code which is run for all tests in the suite. Not all subsystems need
90 put into separate suites, with the type of test as the last element in the suite
92 or similar in the suite name.
94 The full test suite name (including the subsystem name) should be specified as
105   The ``kasan`` subsystem has only one suite, so the suite name is the same as
113   The suite name is ambiguous without the subsystem name.
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
118   unit tests are added, then that suite could be named as ``kasan_unittest`` or
126 results will show up as subtests of the suite's results.
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
150 test name, separated by a colon (i.e. ``suite:test``).
155 Every test suite should be tied to a Kconfig entry.
160   suite.
192 with regular modules, KUnit modules should be named after the test suite,
205 So for the common case, name the file containing the test suite
206 ``tests/<suite>_kunit.c``. The ``tests`` directory should be placed at
210 If the suite name contains some or all of the name of the test's parent
212 redundancy. For example, a ``foo_firmware`` suite could be in the