Home
last modified time | relevance | path

Searched refs:suite (Results 1 – 25 of 71) sorted by relevance

123

/Linux-v5.10/lib/kunit/
Ddebugfs.c40 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_string(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 …]
Dtest.c44 size_t kunit_suite_num_test_cases(struct kunit_suite *suite) in kunit_suite_num_test_cases() argument
49 kunit_suite_for_each_test_case(suite, test_case) in kunit_suite_num_test_cases()
56 static void kunit_print_subtest_start(struct kunit_suite *suite) in kunit_print_subtest_start() argument
58 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "# Subtest: %s", in kunit_print_subtest_start()
59 suite->name); in kunit_print_subtest_start()
60 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "1..%zd", in kunit_print_subtest_start()
61 kunit_suite_num_test_cases(suite)); in kunit_print_subtest_start()
70 struct kunit_suite *suite = is_test ? NULL : test_or_suite; in kunit_print_ok_not_ok() local
81 if (suite) in kunit_print_ok_not_ok()
91 bool kunit_suite_has_succeeded(struct kunit_suite *suite) in kunit_suite_has_succeeded() argument
[all …]
Ddebugfs.h13 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
Dkunit-test.c418 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()
DKconfig23 test suite, which allow users to see results of the last test suite
/Linux-v5.10/crypto/
Dtestmgr.c155 } suite; member
1886 const struct hash_testvec *template = desc->suite.hash.vecs; in alg_test_hash()
1887 unsigned int tcount = desc->suite.hash.count; in alg_test_hash()
2201 const struct aead_test_suite *suite, in generate_aead_message() argument
2213 if (suite->aad_iv && vec->alen >= ivsize) in generate_aead_message()
2251 mutate_aead_message(vec, suite->aad_iv, ivsize); in generate_aead_message()
2254 if (suite->einval_allowed) in generate_aead_message()
2267 const struct aead_test_suite *suite, in generate_random_aead_testvec() argument
2316 generate_aead_message(req, suite, vec, prefer_inauthentic); in generate_random_aead_testvec()
2329 &ctx->test_desc->suite.aead, in try_to_generate_inauthentic_testvec()
[all …]
/Linux-v5.10/Documentation/dev-tools/kunit/
Dstyle.rst24 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 …]
Dusage.rst180 concept of a *test suite*. A *test suite* is just a collection of test cases
204 In the above example the test suite, ``example_test_suite``, would run the test
208 ``kunit_test_suite(example_test_suite)`` registers the test suite with the
212 A test case will only be run if it is associated with a test suite.
215 test suite in a special linker section so that it can be run by KUnit either
608 in ``/sys/kernel/debug/kunit/<test-suite>``. The directory contains one file
611 of the entire suite for the last test run.
/Linux-v5.10/Documentation/devicetree/bindings/mtd/partitions/
Darm,arm-firmware-suite.txt9 - compatible : (required) must be "arm,arm-firmware-suite"
15 compatible = "arm,arm-firmware-suite";
/Linux-v5.10/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt14 - 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.10/tools/testing/selftests/tc-testing/
DREADME1 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
DTODO.txt9 need to better handle problems in pre- and post-suite.
28 and a way to configure a test suite,
/Linux-v5.10/Documentation/arm/vfp/
Drelease-notes.rst14 John R. Hauser using the TestFloat-2a test suite. Details of this
15 library and test suite can be found at:
/Linux-v5.10/include/kunit/
Dtest.h235 int kunit_run_tests(struct kunit_suite *suite);
237 size_t kunit_suite_num_test_cases(struct kunit_suite *suite);
239 unsigned int kunit_test_case_num(struct kunit_suite *suite,
316 #define kunit_test_suite(suite) kunit_test_suites(&suite) argument
318 #define kunit_suite_for_each_test_case(suite, test_case) \ argument
319 for (test_case = suite->test_cases; test_case->run_case; test_case++)
321 bool kunit_suite_has_succeeded(struct kunit_suite *suite);
/Linux-v5.10/Documentation/bpf/
Ds390.rst15 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.10/Documentation/admin-guide/
Dclearing-warn-once.rst9 This can be useful after test suite runs to reproduce problems.
/Linux-v5.10/tools/perf/Documentation/
Dperf-help.txt38 Part of the linkperf:perf[1] suite
/Linux-v5.10/tools/testing/vsock/
DREADME1 AF_VSOCK test suite
/Linux-v5.10/Documentation/input/devices/
Dpxrc.rst44 the `input layer utilities` suite [2]_.
/Linux-v5.10/tools/testing/selftests/livepatch/
DREADME7 The test suite loads and unloads several test kernel modules to verify
/Linux-v5.10/arch/arm/boot/dts/
Dintegrator.dtsi66 compatible = "arm,arm-firmware-suite";
Darm-realview-eb.dtsi123 compatible = "arm,arm-firmware-suite";
133 compatible = "arm,arm-firmware-suite";
/Linux-v5.10/lib/
DKconfig.kgdb53 bool "KGDB: internal test suite"
77 This is the command string to send the kgdb test suite on
DKconfig.kasan174 This is a KUnit test suite doing various nasty things like
185 This is a part of the KASAN test suite that is incompatible with
/Linux-v5.10/net/mac80211/
Dmain.c808 u32 suite = local->hw.wiphy->cipher_suites[r]; in ieee80211_init_cipher_suites() local
810 if (suite == WLAN_CIPHER_SUITE_WEP40 || in ieee80211_init_cipher_suites()
811 suite == WLAN_CIPHER_SUITE_WEP104) in ieee80211_init_cipher_suites()
813 suites[w++] = suite; in ieee80211_init_cipher_suites()

123