Home
last modified time | relevance | path

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

/tools/testing/kunit/test_data/
A Dtest_is_test_passed-no_tests_no_plan.log3 # Subtest: suite
7 ok 1 - suite
A Dtest_parse_subtest_header.log4 # Subtest: suite
7 ok 1 suite
A Dtest_parse_attributes.log4 # Subtest: suite
9 ok 1 suite
A Dtest_parse_ktap_output.log8 ok 1 suite
/tools/testing/selftests/kvm/include/
A Dkvm_test_harness.h26 #define KVM_ONE_VCPU_TEST(suite, test, guestcode) \ argument
29 TEST_F(suite, test) \
/tools/testing/selftests/tc-testing/creating-plugins/
A 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.
/tools/testing/selftests/tc-testing/
A DTODO.txt9 need to better handle problems in pre- and post-suite.
28 and a way to configure a test suite,
A DREADME1 tdc - Linux Traffic Control (tc) unit testing suite
75 One run of tests is considered a "test suite" (this will be refined in the
76 future). A test suite has one or more test cases in it.
153 pre- and post-suite
158 The pre-suite hook receives the number of tests and an array of test ids.
170 - pre (pre-suite)
175 - post (post-suite)
207 first version of the tc testing suite. This work was presented at
/tools/perf/tests/
A Dbuiltin-test.c160 #define test_suite__for_each_test_case(suite, idx) \ argument
161 for (idx = 0; (suite)->test_cases && (suite)->test_cases[idx].name != NULL; idx++)
747 #define for_each_suite(suite) \ in build_suites() argument
749 while ((suite = suites[i][j++]) != NULL) in build_suites()
A Dmake5 # no target specified, trigger the whole suite
/tools/perf/Documentation/
A Dperf-help.txt38 Part of the linkperf:perf[1] suite
A Dperf-bench.txt11 'perf bench' [<common options>] <subsystem> <suite> [<options>]
/tools/testing/vsock/
A DREADME1 AF_VSOCK test suite
42 suite run, e.g.
/tools/testing/memblock/
A DREADME14 difficult. This test suite, usually referred as memblock simulator, is
83 memblock to track valid memory ranges. To achieve this, the test suite registers
/tools/testing/selftests/livepatch/
A DREADME7 The test suite loads and unloads several test kernel modules to verify
/tools/testing/selftests/net/forwarding/
A Dbridge_mld.sh594 group xstats_slave subgroup bridge suite mcast \
600 group xstats_slave subgroup bridge suite mcast \
A Dbridge_igmp.sh593 group xstats_slave subgroup bridge suite mcast \
600 group xstats_slave subgroup bridge suite mcast \
A Dlib.sh885 ip -j stats show dev $if_name group offload subgroup $suite |
/tools/testing/kunit/
A Dkunit.py154 suite, _ = parts
155 if not suites or suites[-1] != suite:
156 suites.append(suite)
/tools/net/sunrpc/xdrgen/
A DREADME255 Build a unit test suite for verifying translation of XDR language
/tools/testing/selftests/bpf/
A DREADME.rst39 question. This can be the name of a test suite or of an individual test. The
/tools/power/pm-graph/
A DREADME49 This tool suite is designed to assist kernel and OS developers in optimizing
156 are waiting for something and when. It also sets a suite of kprobes on

Completed in 29 milliseconds