| /Linux-v5.15/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 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()
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_subtest_start(struct kunit_suite *suite) in kunit_print_subtest_start() argument
139 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "# Subtest: %s", in kunit_print_subtest_start()
140 suite->name); in kunit_print_subtest_start()
141 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "1..%zd", in kunit_print_subtest_start()
142 kunit_suite_num_test_cases(suite)); in kunit_print_subtest_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 | 126 struct kunit_suite *suite; in alloc_fake_suite() local
129 suite = kunit_kzalloc(test, sizeof(*suite), GFP_KERNEL); in alloc_fake_suite()
130 strncpy((char *)suite->name, suite_name, sizeof(suite->name) - 1); in alloc_fake_suite()
132 return suite; in alloc_fake_suite()
|
| D | kunit-test.c | 418 struct kunit_suite *suite = &kunit_log_test_suite; in kunit_log_test() local
422 kunit_log(KERN_INFO, suite, "add to suite log."); in kunit_log_test()
423 kunit_log(KERN_INFO, suite, "along with this."); in kunit_log_test()
431 strstr(suite->log, "add to suite log.")); in kunit_log_test()
433 strstr(suite->log, "along with this.")); in kunit_log_test()
436 KUNIT_EXPECT_PTR_EQ(test, suite->log, (char *)NULL); in kunit_log_test()
|
| D | Kconfig | 24 test suite, which allow users to see results of the last test suite
|
| /Linux-v5.15/crypto/ |
| D | testmgr.c | 158 } suite; member
1880 const struct hash_testvec *template = desc->suite.hash.vecs; in alg_test_hash()
1881 unsigned int tcount = desc->suite.hash.count; in alg_test_hash()
2193 const struct aead_test_suite *suite, in generate_aead_message() argument
2205 if (suite->aad_iv && vec->alen >= ivsize) in generate_aead_message()
2243 mutate_aead_message(vec, suite->aad_iv, ivsize); in generate_aead_message()
2246 if (suite->einval_allowed) in generate_aead_message()
2259 const struct aead_test_suite *suite, in generate_random_aead_testvec() argument
2308 generate_aead_message(req, suite, vec, prefer_inauthentic); in generate_random_aead_testvec()
2321 &ctx->test_desc->suite.aead, in try_to_generate_inauthentic_testvec()
[all …]
|
| /Linux-v5.15/Documentation/dev-tools/kunit/ |
| D | style.rst | 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
[all …]
|
| D | running_tips.rst | 29 this only matches against suite names, but this may change in the future.
217 Retrieving per suite results
221 ``CONFIG_KUNIT_DEBUGFS`` to expose per-suite TAP-formatted results:
229 The results for each suite will be exposed under
230 ``/sys/kernel/debug/kunit/<suite>/results``.
|
| D | usage.rst | 181 concept of a *test suite*. A *test suite* is just a collection of test cases
205 In the above example the test suite, ``example_test_suite``, would run the test
209 ``kunit_test_suite(example_test_suite)`` registers the test suite with the
213 A test case will only be run if it is associated with a test suite.
216 test suite in a special linker section so that it can be run by KUnit either
765 in ``/sys/kernel/debug/kunit/<test-suite>``. The directory contains one file
768 of the entire suite for the last test run.
|
| /Linux-v5.15/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-v5.15/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-v5.15/mm/damon/ |
| D | Kconfig | 20 This builds the DAMON Kunit test suite.
40 This builds the DAMON virtual addresses primitives Kunit test suite.
61 This builds the DAMON debugfs interface Kunit test suite.
|
| /Linux-v5.15/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-v5.15/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-v5.15/include/kunit/ |
| D | test.h | 290 int kunit_run_tests(struct kunit_suite *suite);
292 size_t kunit_suite_num_test_cases(struct kunit_suite *suite);
294 unsigned int kunit_test_case_num(struct kunit_suite *suite,
371 #define kunit_test_suite(suite) kunit_test_suites(&suite) argument
373 #define kunit_suite_for_each_test_case(suite, test_case) \ argument
374 for (test_case = suite->test_cases; test_case->run_case; test_case++)
376 enum kunit_status kunit_suite_has_succeeded(struct kunit_suite *suite);
|
| /Linux-v5.15/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-v5.15/Documentation/admin-guide/ |
| D | clearing-warn-once.rst | 9 This can be useful after test suite runs to reproduce problems.
|
| /Linux-v5.15/lib/ |
| D | Kconfig.kfence | 71 tristate "KFENCE integration test suite" if !KUNIT_ALL_TESTS
75 Test suite for KFENCE, testing various error detection scenarios with
|
| /Linux-v5.15/tools/testing/vsock/ |
| D | README | 1 AF_VSOCK test suite
|
| /Linux-v5.15/tools/perf/Documentation/ |
| D | perf-help.txt | 38 Part of the linkperf:perf[1] suite
|
| /Linux-v5.15/Documentation/input/devices/ |
| D | pxrc.rst | 44 the `input layer utilities` suite [2]_.
|
| /Linux-v5.15/tools/testing/selftests/livepatch/ |
| D | README | 7 The test suite loads and unloads several test kernel modules to verify
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | integrator.dtsi | 66 compatible = "arm,arm-firmware-suite";
|
