| /linux-5.19.10/lib/kunit/ |
| D | debugfs.c | 40 struct kunit_suite *suite, in debugfs_print_result() argument
54 struct kunit_suite *suite = (struct kunit_suite *)seq->private; in debugfs_print_results() local
55 enum kunit_status 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()
63 kunit_suite_for_each_test_case(suite, test_case) in debugfs_print_results()
64 debugfs_print_result(seq, suite, test_case); in debugfs_print_results()
67 kunit_status_to_ok_not_ok(success), 1, suite->name); in debugfs_print_results()
78 struct kunit_suite *suite; in debugfs_results_open() local
80 suite = (struct kunit_suite *)inode->i_private; in debugfs_results_open()
[all …]
|
| D | test.c | 125 size_t kunit_suite_num_test_cases(struct kunit_suite *suite) in kunit_suite_num_test_cases() argument
130 kunit_suite_for_each_test_case(suite, test_case) in kunit_suite_num_test_cases()
137 static void kunit_print_suite_start(struct kunit_suite *suite) in kunit_print_suite_start() argument
139 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "# Subtest: %s", in kunit_print_suite_start()
140 suite->name); in kunit_print_suite_start()
141 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "1..%zd", in kunit_print_suite_start()
142 kunit_suite_num_test_cases(suite)); in kunit_print_suite_start()
152 struct kunit_suite *suite = is_test ? NULL : test_or_suite; in kunit_print_ok_not_ok() local
164 if (suite) in kunit_print_ok_not_ok()
177 enum kunit_status kunit_suite_has_succeeded(struct kunit_suite *suite) in kunit_suite_has_succeeded() argument
[all …]
|
| 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
|
| D | executor_test.c | 211 struct kunit_suite *suite; in alloc_fake_suite() local
214 suite = kunit_kzalloc(test, sizeof(*suite), GFP_KERNEL); in alloc_fake_suite()
215 strncpy((char *)suite->name, suite_name, sizeof(suite->name) - 1); in alloc_fake_suite()
216 suite->test_cases = test_cases; in alloc_fake_suite()
218 return suite; in alloc_fake_suite()
|
| D | kunit-test.c | 453 struct kunit_suite suite; in kunit_log_test() local
455 suite.log = kunit_kzalloc(test, KUNIT_LOG_SIZE, GFP_KERNEL); in kunit_log_test()
456 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, suite.log); in kunit_log_test()
460 kunit_log(KERN_INFO, &suite, "add to suite log."); in kunit_log_test()
461 kunit_log(KERN_INFO, &suite, "along with this."); in kunit_log_test()
469 strstr(suite.log, "add to suite log.")); in kunit_log_test()
471 strstr(suite.log, "along with this.")); in kunit_log_test()
|
| 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()
76 memcpy(copy, suite, sizeof(*copy)); in kunit_filter_tests()
85 kunit_suite_for_each_test_case(suite, test_case) { in kunit_filter_tests()
|
| D | kunit-example-test.c | 47 static int example_test_init_suite(struct kunit_suite *suite) in example_test_init_suite() argument
49 kunit_info(suite, "initializing suite\n"); in example_test_init_suite()
|
| D | Kconfig | 24 test suite, which allow users to see results of the last test suite
|
| /linux-5.19.10/crypto/ |
| D | testmgr.c | 155 } suite; member
1930 const struct hash_testvec *template = desc->suite.hash.vecs; in alg_test_hash()
1931 unsigned int tcount = desc->suite.hash.count; in alg_test_hash()
2244 const struct aead_test_suite *suite, in generate_aead_message() argument
2256 if (suite->aad_iv && vec->alen >= ivsize) in generate_aead_message()
2294 mutate_aead_message(vec, suite->aad_iv, ivsize); in generate_aead_message()
2297 if (suite->einval_allowed) in generate_aead_message()
2310 const struct aead_test_suite *suite, in generate_random_aead_testvec() argument
2359 generate_aead_message(req, suite, vec, prefer_inauthentic); in generate_random_aead_testvec()
2372 &ctx->test_desc->suite.aead, in try_to_generate_inauthentic_testvec()
[all …]
|
| /linux-5.19.10/Documentation/dev-tools/kunit/ |
| D | style.rst | 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
[all …]
|
| D | running_tips.rst | 225 Retrieving per suite results
229 ``CONFIG_KUNIT_DEBUGFS`` to expose per-suite TAP-formatted results:
237 The results for each suite will be exposed under
238 ``/sys/kernel/debug/kunit/<suite>/results``.
|
| /linux-5.19.10/include/kunit/ |
| D | test.h | 172 int (*suite_init)(struct kunit_suite *suite);
173 void (*suite_exit)(struct kunit_suite *suite);
233 int kunit_run_tests(struct kunit_suite *suite);
235 size_t kunit_suite_num_test_cases(struct kunit_suite *suite);
237 unsigned int kunit_test_case_num(struct kunit_suite *suite,
314 #define kunit_test_suite(suite) kunit_test_suites(&suite) argument
341 #define kunit_test_init_section_suite(suite) \ argument
342 kunit_test_init_section_suites(&suite)
344 #define kunit_suite_for_each_test_case(suite, test_case) \ argument
345 for (test_case = suite->test_cases; test_case->run_case; test_case++)
[all …]
|
| /linux-5.19.10/tools/testing/kunit/test_data/ |
| D | test_is_test_passed-no_tests_no_plan.log | 3 # Subtest: suite
7 ok 1 - suite
|
| /linux-5.19.10/Documentation/devicetree/bindings/mtd/partitions/ |
| D | arm,arm-firmware-suite.txt | 9 - compatible : (required) must be "arm,arm-firmware-suite"
15 compatible = "arm,arm-firmware-suite";
|
| /linux-5.19.10/tools/testing/selftests/tc-testing/creating-plugins/ |
| 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-5.19.10/tools/testing/selftests/tc-testing/ |
| 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
|
| D | TODO.txt | 9 need to better handle problems in pre- and post-suite.
28 and a way to configure a test suite,
|
| /linux-5.19.10/Documentation/arm/vfp/ |
| 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-5.19.10/mm/damon/ |
| D | Kconfig | 20 This builds the DAMON Kunit test suite.
48 This builds the DAMON virtual addresses operations Kunit test suite.
76 This builds the DAMON debugfs interface Kunit test suite.
|
| /linux-5.19.10/lib/ |
| D | Kconfig.kfence | 55 Warning: The KUnit test suite fails with this option enabled - due to
87 tristate "KFENCE integration test suite" if !KUNIT_ALL_TESTS
91 Test suite for KFENCE, testing various error detection scenarios with
|
| /linux-5.19.10/Documentation/bpf/ |
| 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-5.19.10/Documentation/admin-guide/ |
| D | clearing-warn-once.rst | 9 This can be useful after test suite runs to reproduce problems.
|
| /linux-5.19.10/tools/perf/Documentation/ |
| D | perf-help.txt | 38 Part of the linkperf:perf[1] suite
|
| /linux-5.19.10/tools/testing/vsock/ |
| D | README | 1 AF_VSOCK test suite
|
| /linux-5.19.10/Documentation/input/devices/ |
| D | pxrc.rst | 44 the `input layer utilities` suite [2]_.
|