| /linux/lib/kunit/ |
| A D | debugfs.c | 40 struct kunit_suite *suite, in debugfs_print_result() argument
55 bool success = kunit_suite_has_succeeded(suite); in debugfs_print_results()
58 if (!suite || !suite->log) in debugfs_print_results()
61 seq_printf(seq, "%s", suite->log); in debugfs_print_results()
64 debugfs_print_result(seq, suite, test_case); in debugfs_print_results()
78 struct kunit_suite *suite; in debugfs_results_open() local
101 suite->debugfs = debugfs_create_dir(suite->name, debugfs_rootdir); in kunit_debugfs_create_suite()
104 suite->debugfs, in kunit_debugfs_create_suite()
105 suite, &debugfs_results_fops); in kunit_debugfs_create_suite()
112 debugfs_remove_recursive(suite->debugfs); in kunit_debugfs_destroy_suite()
[all …]
|
| A D | test.c | 140 suite->name); in kunit_print_subtest_start()
164 if (suite) in kunit_print_ok_not_ok()
200 suite->name, in kunit_print_subtest_end()
322 if (suite->init) { in kunit_run_case_internal()
325 ret = suite->init(test); in kunit_run_case_internal()
348 if (suite->exit) in kunit_run_case_cleanup()
349 suite->exit(test); in kunit_run_case_cleanup()
364 struct kunit_suite *suite = ctx->suite; in kunit_try_run_case() local
383 struct kunit_suite *suite = ctx->suite; in kunit_catch_run_case() local
431 context.suite = suite; in kunit_run_case_catch_errors()
[all …]
|
| A D | debugfs.h | 13 void kunit_debugfs_create_suite(struct kunit_suite *suite);
14 void kunit_debugfs_destroy_suite(struct kunit_suite *suite);
20 static inline void kunit_debugfs_create_suite(struct kunit_suite *suite) { } in kunit_debugfs_create_suite() argument
22 static inline void kunit_debugfs_destroy_suite(struct kunit_suite *suite) { } in kunit_debugfs_destroy_suite() argument
|
| A D | executor_test.c | 209 struct kunit_suite *suite; in alloc_fake_suite() local
212 suite = kunit_kzalloc(test, sizeof(*suite), GFP_KERNEL); in alloc_fake_suite()
213 strncpy((char *)suite->name, suite_name, sizeof(suite->name) - 1); in alloc_fake_suite()
214 suite->test_cases = test_cases; in alloc_fake_suite()
216 return suite; in alloc_fake_suite()
|
| A D | kunit-test.c | 418 struct kunit_suite suite; in kunit_log_test() local
420 suite.log = kunit_kzalloc(test, KUNIT_LOG_SIZE, GFP_KERNEL); in kunit_log_test()
421 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, suite.log); in kunit_log_test()
425 kunit_log(KERN_INFO, &suite, "add to suite log."); in kunit_log_test()
426 kunit_log(KERN_INFO, &suite, "along with this."); in kunit_log_test()
434 strstr(suite.log, "add to suite log.")); in kunit_log_test()
436 strstr(suite.log, "along with this.")); in kunit_log_test()
|
| A D | executor.c | 58 kunit_filter_tests(struct kunit_suite *const suite, const char *test_glob) in kunit_filter_tests() argument
64 kunit_suite_for_each_test_case(suite, test_case) { in kunit_filter_tests()
74 memcpy(copy, suite, sizeof(*copy)); in kunit_filter_tests()
79 kunit_suite_for_each_test_case(suite, test_case) { in kunit_filter_tests()
|
| A D | Kconfig | 24 test suite, which allow users to see results of the last test suite
|
| /linux/crypto/ |
| A D | testmgr.c | 158 } suite; member
4152 .suite = {
4159 .suite = {
4165 .suite = {
4171 .suite = {
4177 .suite = {
4184 .suite = {
4190 .suite = {
4197 .suite = {
4207 .suite = {
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| A D | style.rst | 83 shutdown code which is run for all tests in the suite.
94 similar in the suite name.
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
129 will show up as subtests of the suite's results.
153 test name, separated by a colon (i.e. ``suite:test``).
158 Every test suite should be tied to a Kconfig entry.
163 suite.
199 ``<suite>_test.c`` (or, as above, ``<suite>_kunit.c``). This file should be
[all …]
|
| A D | running_tips.rst | 224 Retrieving per suite results
228 ``CONFIG_KUNIT_DEBUGFS`` to expose per-suite TAP-formatted results:
236 The results for each suite will be exposed under
237 ``/sys/kernel/debug/kunit/<suite>/results``.
|
| /linux/tools/testing/selftests/tc-testing/creating-plugins/ |
| A D | AddingPlugins.txt | 14 - adding commands to be run before and/or after the test suite
18 pre (the pre-suite stage)
23 post (the post-suite stage)
48 TAP output. The tdc.py script will do that for the test suite as
52 post-suite method using this info passed in to the pre_suite method.
|
| /linux/Documentation/devicetree/bindings/mtd/partitions/ |
| A D | arm,arm-firmware-suite.txt | 9 - compatible : (required) must be "arm,arm-firmware-suite"
15 compatible = "arm,arm-firmware-suite";
|
| /linux/tools/testing/selftests/tc-testing/ |
| A D | README | 1 tdc - Linux Traffic Control (tc) unit testing suite
76 One run of tests is considered a "test suite" (this will be refined in the
77 future). A test suite has one or more test cases in it.
134 -P, --pause Pause execution just before post-suite stage
198 pre- and post-suite
203 The pre-suite hook receives the number of tests and an array of test ids.
215 - pre (pre-suite)
220 - post (post-suite)
254 first version of the tc testing suite. This work was presented at
|
| A D | TODO.txt | 9 need to better handle problems in pre- and post-suite.
28 and a way to configure a test suite,
|
| /linux/mm/damon/ |
| A D | Kconfig | 20 This builds the DAMON Kunit test suite.
48 This builds the DAMON virtual addresses primitives Kunit test suite.
69 This builds the DAMON debugfs interface Kunit test suite.
|
| /linux/Documentation/arm/vfp/ |
| A D | release-notes.rst | 14 John R. Hauser using the TestFloat-2a test suite. Details of this
15 library and test suite can be found at:
|
| /linux/include/kunit/ |
| A D | test.h | 299 int kunit_run_tests(struct kunit_suite *suite);
301 size_t kunit_suite_num_test_cases(struct kunit_suite *suite);
303 unsigned int kunit_test_case_num(struct kunit_suite *suite,
380 #define kunit_test_suite(suite) kunit_test_suites(&suite) argument
382 #define kunit_suite_for_each_test_case(suite, test_case) \ argument
383 for (test_case = suite->test_cases; test_case->run_case; test_case++)
385 enum kunit_status kunit_suite_has_succeeded(struct kunit_suite *suite);
|
| /linux/Documentation/bpf/ |
| A D | s390.rst | 15 The following is required to build and run the test suite:
105 In addition to the usual Kconfig options required to run the BPF test suite, it
127 4. Running the test suite
160 After that, the test suite can be run using the following commands::
|
| /linux/Documentation/admin-guide/ |
| A D | clearing-warn-once.rst | 9 This can be useful after test suite runs to reproduce problems.
|
| /linux/lib/ |
| A D | Kconfig.kfence | 75 tristate "KFENCE integration test suite" if !KUNIT_ALL_TESTS
79 Test suite for KFENCE, testing various error detection scenarios with
|
| /linux/tools/testing/kunit/ |
| A D | kunit.py | 117 suite, case = parts
118 if not suites or suites[-1] != suite:
119 suites.append(suite)
|
| /linux/tools/perf/Documentation/ |
| A D | perf-help.txt | 38 Part of the linkperf:perf[1] suite
|
| /linux/tools/testing/vsock/ |
| A D | README | 1 AF_VSOCK test suite
|
| /linux/Documentation/input/devices/ |
| A D | pxrc.rst | 44 the `input layer utilities` suite [2]_.
|
| /linux/tools/testing/selftests/livepatch/ |
| A D | README | 7 The test suite loads and unloads several test kernel modules to verify
|