Lines Matching refs:suite

24 and subsystems. A test suite is a group of tests which test a related area of
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
83 shutdown code which is run for all tests in the suite.
92 separate suites, with the type of test as the last element in the suite name.
94 similar in the suite name.
96 The full test suite name (including the subsystem name) should be specified as
109   The ``kasan`` subsystem has only one suite, so the suite name is the same as
117   The suite name is ambiguous without the subsystem name.
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
122   tests be added, then that suite could be named ``kasan_unittest`` or similar.
129 will show up as subtests of the suite's results.
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``).
158 Every test suite should be tied to a Kconfig entry.
163   suite.
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
199 ``<suite>_test.c`` (or, as above, ``<suite>_kunit.c``). This file should be
202 If the suite name contains some or all of the name of the test's parent
204 For example, a ``foo_firmware`` suite could be in the ``foo/firmware_test.c``