Searched refs:suites (Results 1 – 14 of 14) sorted by relevance
| /linux/tools/perf/tests/ |
| H A D | builtin-test.c | 474 static int __cmd_test(struct test_suite **suites, int argc, const char *argv[], in __cmd_test() argument
480 for (struct test_suite **t = suites; *t; t++) { in __cmd_test()
526 for (struct test_suite **t = suites; *t; t++, curr_suite++) { in __cmd_test()
586 static int perf_test__list(FILE *fp, struct test_suite **suites, int argc, const char **argv) in perf_test__list() argument
590 for (struct test_suite **t = suites; *t; t++, curr_suite++) { in perf_test__list()
648 static struct test_suite **suites[] = { in build_suites() local
657 if (suites[2] == NULL) in build_suites()
658 suites[2] = create_script_test_suites(); in build_suites()
661 for (size_t i = 0, j = 0; i < ARRAY_SIZE(suites); i++, j = 0) \ in build_suites()
662 while ((suite = suites[i][j++]) != NULL) in build_suites()
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | style.rst | 23 To make tests easy to find, they are grouped into suites and subsystems. A test
25 is a set of test suites which test different parts of a kernel subsystem
32 or more KUnit test suites which test the same driver or part of the kernel. A
72 a way of categorizing test suites and naming modules which provides a
79 KUnit tests are grouped into test suites, which cover a specific area of
80 functionality being tested. Test suites can have shared initialization and
82 to be split into multiple test suites (for example, simple drivers).
84 Test suites are named after the subsystem they are part of. If a subsystem
85 contains several suites, the specific area under test should be appended to the
90 put into separate suites, with the type of test as the last element in the suite
[all …]
|
| H A D | run_manual.rst | 89 However, this feature is not available with KUnit suites that use init data,
91 suites that use init data should be defined using the
|
| H A D | architecture.rst | 27 into suites. A KUnit test case is a function with type signature
47 A KUnit suite includes a collection of test cases. The KUnit suites
78 The Test suites are stored in a linker section
|
| H A D | running_tips.rst | 281 Test suites and cases can be marked with test attributes, such as speed of
308 Test suites can be marked with an attribute by setting the "attr" field in the
343 This is an example of how test attributes for test suites will be formatted in
407 Since both suites and test cases can have attributes, there may be conflicts
|
| H A D | index.rst | 28 of test cases called test suites. The tests either run on kernel boot
|
| /linux/tools/testing/selftests/tc-testing/ |
| H A D | TODO.txt | 29 to automate running multiple "test suites" with different requirements
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-bench.txt | 6 perf-bench - General framework for benchmark suites
15 This 'perf bench' command is a general framework for benchmark suites.
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | Kconfig | 42 It is meant to be used by SCMI compliance/testing suites.
|
| /linux/Documentation/gpu/ |
| H A D | todo.rst | 653 Clean up and document former selftests suites
656 Some KUnit test suites (drm_buddy, drm_cmdline_parser, drm_damage_helper,
658 drm_rect) are former selftests suites that have been converted over when KUnit
661 These suites were fairly undocumented, and with different goals than what unit
662 tests can be. Trying to identify what each test in these suites actually test
|
| /linux/Documentation/rust/ |
| H A D | testing.rst | 68 For the kernel, however, these tests get transformed into KUnit test suites.
|
| /linux/Documentation/mm/ |
| H A D | hwpoison.rst | 116 some early filtering to avoid corrupted unintended pages in test suites.
|
| /linux/Documentation/networking/dsa/ |
| H A D | configuration.rst | 8 network configuration suites by now and has to be performed manually.
|
| /linux/ |
| H A D | CREDITS | 2934 D: AX.25, NET/ROM and ROSE amateur radio protocol suites
|