| /openbmc/openbmc/poky/meta/lib/oeqa/core/decorator/ |
| H A D | depends.py | 34 def _validate_test_case_depends(cases, depends): argument
36 if not case in cases:
39 if not dep in cases:
41 ", cases available %s." % (case, dep, str(cases.keys())))
43 def _order_test_case_by_depends(cases, depends): argument
55 dep_graph['__root__'] = cases.keys()
56 for case in cases:
66 return [cases[case_id] for case_id in cases_ordered]
|
| /openbmc/qemu/scripts/ |
| H A D | device-crash-test | 442 cases = [testcase.copy()]
445 cases = genCases1(args, cases, var, fn)
446 return cases
450 cases = genCases(args, testcase)
452 cases = list(cases)
453 cases = random.sample(cases, min(args.random, len(cases)))
455 cases = list(cases)
456 dbg("%d test cases to test", len(cases))
458 cases = list(cases)
459 random.shuffle(cases)
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/mcelog/mce-test/ |
| H A D | makefile-remove-ldflags.patch | 7 diff --git a/cases/stress/hwpoison/Makefile b/cases/stress/hwpoison/Makefile
9 --- a/cases/stress/hwpoison/Makefile
10 +++ b/cases/stress/hwpoison/Makefile
|
| H A D | 0001-gcov_merge.py-scov_merge.py-switch-to-python3.patch | 24 # Merge gcov graph from several test cases. This can be used to check
25 # the coverage of several test cases.
70 # Merge mce serverity coverage file from several test cases. This can
71 # be used to check the coverage of several test cases.
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | oeqa-fvp.md | 3 …ng the `testimage` Yocto task. meta-arm has good support for writing test cases against [Arm FVPs]…
24 As in OEQA in OE-core, tests cases can run commands on the machine using SSH. It therefore requires…
32 For examples of test cases, see meta/lib/oeqa/runtime/cases in OE-Core. The majority of test cases …
36 To support firmware and baremetal testing, OEFVPTarget also allows test cases to make assertions ag…
44 For an example of a full test case, see meta-arm/lib/oeqa/runtime/cases/linuxboot.py This test case…
|
| /openbmc/openbmc/poky/scripts/lib/resulttool/ |
| H A D | manualexecution.py | 123 cases = load_json_file(case_file)
133 for case in copy.deepcopy(cases) :
135 cases.remove(case)
137 print('\nTotal number of test cases in this test suite: %s\n' % len(cases))
138 for c in cases:
194 cases = load_json_file(case_file)
200 for case in cases:
|
| /openbmc/openbmc-test-automation/test_lists/ |
| H A D | skip_test_witherspoon | 8 # System LED test cases which are NA for Witherspoon system.
46 # Configure invalid IP address use cases.
57 # Skipping RAS test cases
67 # IPMI disable and enable use cases.
|
| /openbmc/linux/scripts/coccinelle/misc/ |
| H A D | cond_no_effect.cocci | 5 // There can be false positives in cases where the positional
7 // is a placeholder for not yet handled cases.
17 // the two known cases are:
38 // All other cases look like bugs or at least lack of documentation
|
| /openbmc/openbmc-test-automation/test_lists/witherspoon/ |
| H A D | skip_inband_ipmi | 1 #Skipping inband IPMI test cases to run all out-of-band IPMI test cases
|
| H A D | skip_oob_ipmi | 1 #Skipping out-of-band IPMI test cases to run all inband IPMI test cases
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 41 In some cases it is legitimate to omit specific functions from the trace,
42 but all other functions must be reported. These cases are described in
45 Secondly, the reliable stacktrace function must be robust to cases where
47 function should attempt to detect such cases and return a non-zero error
49 an unsafe way. Specific cases are described in further detail below.
55 To ensure that kernel code can be correctly unwound in all cases,
63 In some cases, an unwinder may require metadata to correctly unwind.
115 To ensure that such cases do not result in functions being omitted from a
148 Architectures which cannot identify when it is reliable to unwind such cases
154 Architectures which can identify when it is reliable to unwind such cases (or
[all …]
|
| /openbmc/linux/tools/testing/selftests/tc-testing/ |
| H A D | README | 59 cases. To disable execution within the namespace, pass the -N option
77 future). A test suite has one or more test cases in it.
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
131 Execute test cases that use a physical device, where
137 select which test cases: files plus directories; filtered by categories
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
[all …]
|
| /openbmc/linux/net/bluetooth/ |
| H A D | Kconfig | 130 cases are run first thing at module load time. When the Bluetooth
131 subsystem is compiled into the kernel image, then the test cases
135 bool "ECDH test cases"
138 Run test cases for ECDH cryptographic functionality used by the
142 bool "SMP test cases"
145 Run test cases for SMP cryptographic functionality, including both
|
| /openbmc/linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | libbpf_probes.c | 98 } cases[] = { in test_libbpf_probe_helpers() local
109 size_t case_cnt = ARRAY_SIZE(cases), i; in test_libbpf_probe_helpers()
113 const struct case_def *d = &cases[i]; in test_libbpf_probe_helpers()
|
| /openbmc/openbmc-test-automation/ |
| H A D | README.md | 166 `redfish/`: Contains the general test cases for OpenBMC stack functional
169 `systest/`: Contains test cases for HTX bootme testing.
171 `xcat/`: Contains test cases for XCAT automation.
173 `gui/test/`: Contains test cases for testing web-based interface built on
176 `gui/gui_test/`: Contains test cases for testing web-based user interface built
179 `pldm/`: Contains test cases for platform management subsystem (base, bios, fru,
182 `snmp/`: Contains test cases for SNMP (Simple Network Management Protocol)
185 `openpower/`: Contains test cases for an OpenPOWER based system.
191 `test_list/`: Contains the argument files used for skipping test cases (e.g
201 `redfish/`: Contains test cases for DMTF Redfish-related feature supported on
[all …]
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_request_via_mTLS.md | 59 purposes. Therefore, some test cases need to write a new one to match it for
61 username) Some cases don’t need to be tested because the purpose of them are
76 Most cases related to sessions don't require mTLS because Redfish requests
78 these cases when mTLS is enabled.
|
| /openbmc/linux/tools/testing/selftests/rcutorture/doc/ |
| H A D | TINY_RCU.txt | 1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-async-timeout_4.0.3.bb | 3 The context manager is useful in cases when you want to apply \
4 timeout logic around block of code or in cases when asyncio.wait_for() \
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | testing.md | 5 The [test](../test) directory contains automated test cases written using the
9 The goal is to write automated test cases for as much application code as
36 CI test environment. Thus, in automated test cases they need to be mocked.
|
| /openbmc/qemu/scripts/simplebench/ |
| H A D | img_bench_templater.py | 89 cases = [{'id': ' / '.join(x), 'data': x} for x in templater.rows] variable
91 result = simplebench.bench(bench_func, envs, cases, count=5,
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | rcuref.rst | 11 those unusual cases where percpu-ref would consume too much memory,
82 update (write) stream. In such cases, atomic_inc_not_zero() might be
84 use atomic_inc() in such cases.
87 search_and_reference() code path. In such cases, the
139 In cases where delete() can sleep, synchronize_rcu() can be called from
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | usage.rst | 66 additional tests cases which would test each property that an ``add`` function
164 We need many test cases covering all the unit's behaviors. It is common to have
167 *test suite*. A test suite is a collection of test cases for a unit of code
196 ``example_suite_init``, then run the test cases ``example_test_foo``,
229 not depend on physical hardware. Some of our test cases may not need hardware,
262 however, it is an easily derived concept. Accordingly, in most cases, every
499 In complicated cases, we recommend using a *table-driven test* compared to the
512 struct sha1_test_case cases[] = {
522 for (i = 0; i < ARRAY_SIZE(cases); ++i) {
523 sha1sum(cases[i].str, out);
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm/lib/oeqa/selftest/cases/ |
| H A D | runfvp.py | 44 cases = list(testdir.glob("auto-*.json"))
45 if not cases:
47 for case in cases:
|
| /openbmc/openbmc/poky/meta/recipes-core/readline/readline/ |
| H A D | norpath.patch | 3 cases this is necessary but our use cases aren't one of them.
|
| /openbmc/openbmc-test-automation/gui/ |
| H A D | __init__.robot | 2 Documentation Main initialization file for the test cases contained in this
23 [Documentation] Display initial info about the test cases.
|