Home
last modified time | relevance | path

Searched full:suite (Results 1 – 25 of 466) sorted by relevance

12345678910>>...19

/Linux-v6.1/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 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 …]
Dtest.c138 size_t kunit_suite_num_test_cases(struct kunit_suite *suite) in kunit_suite_num_test_cases() argument
143 kunit_suite_for_each_test_case(suite, test_case) in kunit_suite_num_test_cases()
150 static void kunit_print_suite_start(struct kunit_suite *suite) in kunit_print_suite_start() argument
152 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "# Subtest: %s", in kunit_print_suite_start()
153 suite->name); in kunit_print_suite_start()
154 kunit_log(KERN_INFO, suite, KUNIT_SUBTEST_INDENT "1..%zd", in kunit_print_suite_start()
155 kunit_suite_num_test_cases(suite)); in kunit_print_suite_start()
165 struct kunit_suite *suite = is_test ? NULL : test_or_suite; in kunit_print_ok_not_ok() local
170 * We do not log the test suite results as doing so would in kunit_print_ok_not_ok()
171 * mean debugfs display would consist of the test suite in kunit_print_ok_not_ok()
[all …]
Dkunit-example-test.c44 * This is run once before all test cases in the suite.
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()
127 * Here we make a list of all the test cases we want to add to the test suite
135 * test suite.
145 * This defines a suite or grouping of tests.
147 * Test cases are defined as belonging to the suite by adding them to
154 * cleanup. For clarity, running tests in a test suite would behave as follows:
156 * suite.suite_init(suite);
157 * suite.init(test);
[all …]
Dexecutor_test.c29 kunit_parse_filter_glob(&filter, "suite"); in parse_filter_test()
30 KUNIT_EXPECT_STREQ(test, filter.suite_glob, "suite"); in parse_filter_test()
35 kunit_parse_filter_glob(&filter, "suite.test"); in parse_filter_test()
36 KUNIT_EXPECT_STREQ(test, filter.suite_glob, "suite"); in parse_filter_test()
149 struct kunit_suite *suite; in alloc_fake_suite() local
152 suite = kunit_kzalloc(test, sizeof(*suite), GFP_KERNEL); in alloc_fake_suite()
153 strncpy((char *)suite->name, suite_name, sizeof(suite->name) - 1); in alloc_fake_suite()
154 suite->test_cases = test_cases; in alloc_fake_suite()
156 return suite; in alloc_fake_suite()
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
Dexecutor.c56 /* Create a copy of suite with only tests that match test_glob. */
58 kunit_filter_tests(const 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()
72 copy = kmemdup(suite, sizeof(*copy), GFP_KERNEL); in kunit_filter_tests()
83 kunit_suite_for_each_test_case(suite, test_case) { in kunit_filter_tests()
213 if (filter_glob_param) { /* a copy was made of each suite */ in kunit_run_all_tests()
Dkunit-test.c460 struct kunit_suite suite; in kunit_log_test() local
462 suite.log = kunit_kzalloc(test, KUNIT_LOG_SIZE, GFP_KERNEL); in kunit_log_test()
463 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, suite.log); in kunit_log_test()
467 kunit_log(KERN_INFO, &suite, "add to suite log."); in kunit_log_test()
468 kunit_log(KERN_INFO, &suite, "along with this."); in kunit_log_test()
476 strstr(suite.log, "add to suite log.")); in kunit_log_test()
478 strstr(suite.log, "along with this.")); in kunit_log_test()
/Linux-v6.1/Documentation/dev-tools/kunit/
Dstyle.rst24 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 …]
Darchitecture.rst48 A KUnit suite includes a collection of test cases. The KUnit suites
68 In the above example, the test suite ``example_test_suite``, runs the
72 The ``kunit_test_suite(example_test_suite)`` registers the test suite
88 :alt: KUnit Suite Memory
90 KUnit Suite Memory Diagram
Dstart.rst128 separator between the name of the test suite and the test case,
129 otherwise, it will be interpreted as the name of the test suite.
132 a. inform the name of a test suite, like ``"kunit_executor_test"``,
137 b. inform the name of a test case prefixed by its test suite,
144 any test suite::
/Linux-v6.1/crypto/
Dtestmgr.c155 } 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-v6.1/tools/perf/Documentation/
Dperf-bench.txt11 'perf bench' [<common options>] <subsystem> <suite> [<options>]
76 Suite for evaluating performance of scheduler and IPC mechanisms.
115 Suite for pipe() system call.
146 Suite for evaluating performance of core system call throughput (both usecs/op and ops/sec metrics).
154 Suite for evaluating performance of simple memory copy in various ways.
178 Suite for evaluating performance of simple memory set in various ways.
204 Suite for evaluating NUMA workloads.
209 Suite for evaluating hash tables.
212 Suite for evaluating wake calls.
215 Suite for evaluating parallel wake calls.
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/mtd/partitions/
Darm,arm-firmware-suite.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/arm,arm-firmware-suite.yaml#
7 title: ARM Firmware Suite (AFS) Partitions
13 The ARM Firmware Suite is a flash partitioning system found on the
19 const: arm,arm-firmware-suite
26 compatible = "arm,arm-firmware-suite";
/Linux-v6.1/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-v6.1/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.txt1 tc Testing Suite To-Do list:
9 need to better handle problems in pre- and post-suite.
28 and a way to configure a test suite,
/Linux-v6.1/tools/testing/kunit/
Dkunit_tool_test.py226 # A skipped test does not fail the whole suite.
245 # A skipped test does not fail the whole suite.
753 want = ['suite.test1', 'suite.test2', 'suite2.test1']
757 kunit.KunitExecRequest(None, None, '.kunit', 300, 'suite*', None, 'suite'))
762 args=['kunit.action=list'], build_dir='.kunit', filter_glob='suite*', timeout=300)
767 mock_tests.return_value = ['suite.test1', 'suite.test2', 'suite2.test1']
768 kunit.main(['exec', '--run_isolated=suite', 'suite*.test*'])
772 kunit.KunitExecRequest(None, None, '.kunit', 300, 'suite*.test*', None, 'suite'))
774 mock.call(args=None, build_dir='.kunit', filter_glob='suite.test*', timeout=300),
780 mock_tests.return_value = ['suite.test1', 'suite.test2', 'suite2.test1']
[all …]
Dkunit.py134 …raise ValueError(f'internal KUnit error, test name should be of the form "<suite>.<test>", got "{t…
135 suite, case = parts
136 if not suites or suites[-1] != suite:
137 suites.append(suite)
148 if request.run_isolated == 'suite':
355 'individual suite/test. This is can be useful for debugging '
359 choices=['suite', 'test'])
/Linux-v6.1/tools/testing/kunit/test_data/
Dtest_is_test_passed-no_tests_no_plan.log3 # Subtest: suite
7 ok 1 - suite
/Linux-v6.1/include/kunit/
Dtest.h50 * enum kunit_status - Type of result for a test or test suite
51 * @KUNIT_SUCCESS: Denotes the test suite has not failed nor been skipped
72 * with a &struct kunit_suite and will be run after the suite's init
73 * function and followed by the suite's exit function.
156 * @suite_init: called once per test suite before the test cases.
157 * @suite_exit: called once per test suite after all test cases.
172 int (*suite_init)(struct kunit_suite *suite);
173 void (*suite_exit)(struct kunit_suite *suite);
235 int kunit_run_tests(struct kunit_suite *suite);
237 size_t kunit_suite_num_test_cases(struct kunit_suite *suite);
[all …]
/Linux-v6.1/mm/damon/
DKconfig20 This builds the DAMON Kunit test suite.
48 This builds the DAMON virtual addresses operations Kunit test suite.
79 This builds the DAMON debugfs interface Kunit test suite.
/Linux-v6.1/lib/
DKconfig.kfence55 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-v6.1/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-v6.1/include/linux/
Dieee80211.h3943 #define SUITE(oui, id) (((oui) << 8) | (id)) macro
3945 /* cipher suite selectors */
3946 #define WLAN_CIPHER_SUITE_USE_GROUP SUITE(0x000FAC, 0)
3947 #define WLAN_CIPHER_SUITE_WEP40 SUITE(0x000FAC, 1)
3948 #define WLAN_CIPHER_SUITE_TKIP SUITE(0x000FAC, 2)
3949 /* reserved: SUITE(0x000FAC, 3) */
3950 #define WLAN_CIPHER_SUITE_CCMP SUITE(0x000FAC, 4)
3951 #define WLAN_CIPHER_SUITE_WEP104 SUITE(0x000FAC, 5)
3952 #define WLAN_CIPHER_SUITE_AES_CMAC SUITE(0x000FAC, 6)
3953 #define WLAN_CIPHER_SUITE_GCMP SUITE(0x000FAC, 8)
[all …]
/Linux-v6.1/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:

12345678910>>...19