/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 49 raise OEQADependency("Test cases %s and %s have a circular" \ 55 dep_graph['__root__'] = cases.keys() 56 for case in cases: 66 return [cases[case_id] for case_id in cases_ordered] 92 _validate_test_case_depends(registry['cases'], registry['depends']) [all …]
|
H A D | __init__.py | 38 # OETestLoader call it when is loading test cases. 42 # registry) of a cases that were filtered. 60 # OETestLoader call it after discover test cases 61 # needs to return the cases to be run. 64 return registry['cases']
|
/openbmc/openbmc/poky/meta/lib/oeqa/manual/ |
H A D | kernel-dev.json | 17 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi… 18 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik… 39 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi… 40 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik… 61 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi… 62 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik… 83 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi… 84 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik… 105 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi… 106 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik… [all …]
|
/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/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/qemu/scripts/ |
H A D | device-crash-test | 61 # because unexpected cases where QEMU exits with exitcode=1 will 440 """Generate test cases for all variables 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)) [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/openbmc/poky/meta/lib/oeqa/core/ |
H A D | loader.py | 108 self.tc._registry['cases'][case_id] = case 140 # 'auto' is a reserved key word to run test cases automatically 222 Returns a suite of all tests cases contained in testCaseClass. 225 raise TypeError("Test cases should not be derived from TestSuite." \ 263 for case in self.tc._registry['cases']: 270 raise OEQATestNotFound("Not found %s in loaded test cases" % \ 281 cases = None 285 cases = clss.discover(self.tc._registry) 290 return self.suiteClass(cases) if cases else big_suite 330 Returns a suite of all tests cases contained in module. [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
|
/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/openbmc-test-automation/ |
H A D | README.md | 156 `redfish/`: Contains the general test cases for OpenBMC stack functional 159 `systest/`: Contains test cases for HTX bootme testing. 161 `xcat/`: Contains test cases for XCAT automation. 163 `gui/test/`: Contains test cases for testing web-based interface built on 166 `gui/gui_test/`: Contains test cases for testing web-based user interface built 169 `pldm/`: Contains test cases for platform management subsystem (base, bios, fru, 172 `snmp/`: Contains test cases for SNMP (Simple Network Management Protocol) 175 `openpower/`: Contains test cases for an OpenPOWER based system. 181 `test_list/`: Contains the argument files used for skipping test cases (e.g 191 `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 | 56 ## Test Cases for mTLS authentication 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/Documentation/dev-tools/kunit/ |
H A D | usage.rst | 6 Test Cases 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) { [all …]
|
/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.
|
H A D | skip_test_palmetto | 20 # Test cases are NA for Palmetto 31 # System LED test cases which are NA for Palmetto system. 40 # FSI Related Test Cases NA for Palmetto System.
|
/openbmc/qemu/tests/tcg/riscv64/ |
H A D | test-div.c | 9 { 4, 2, 2, 0 }, /* normal cases */ 11 { 0, 0, -1, 0 }, /* div by zero cases */ 21 { 4, 2, 2, 0 }, /* normal cases */ 23 { 0, 0, ULONG_MAX, 0 }, /* div by zero cases */
|
/openbmc/openbmc/poky/scripts/lib/resulttool/ |
H A D | manualexecution.py | 1 # test case management tool - manual execution from testopia test cases 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: 235 … help='make the testcase configuration file to run a set of test cases based on user selection')
|
/openbmc/qemu/scripts/simplebench/ |
H A D | img_bench_templater.py | 65 row templating: [var1|var2|...] - similar thing to define rows (test-cases) 70 qemu-img-new in your build directory in two test-cases with 4K writes and 64K 79 test-cases). 89 cases = [{'id': ' / '.join(x), 'data': x} for x in templater.rows] variable 91 result = simplebench.bench(bench_func, envs, cases, count=5,
|
/openbmc/phosphor-power/phosphor-regulators/test/ |
H A D | mock_services.hpp | 91 * This allows test cases to use the object in EXPECT_CALL() statements. 103 * This allows test cases to use the object in EXPECT_CALL() statements. 116 * This allows test cases to use the object in EXPECT_CALL() statements. 128 * This allows test cases to use the object in EXPECT_CALL() statements. 140 * This allows test cases to use the object in EXPECT_CALL() statements.
|
/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/linux/tools/testing/selftests/tc-testing/creating-testcases/ |
H A D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc 5 ADDING TEST CASES 10 template.json for the required JSON format for test cases. 18 If you wish to store your custom test cases elsewhere, be sure to run 83 in the test cases. tdc will output a series of TAP results for the skipped
|
/openbmc/linux/tools/usb/ |
H A D | hcd-tests.sh | 37 # NOTE: the 'in' and 'out' cases are usually bulk, but can be 106 echo '** Control test cases:' 124 echo '** Host Write (OUT) test cases:' 155 echo '** Host ISOCHRONOUS Write (OUT) test cases:' 182 echo '** Host Read (IN) test cases:' 208 echo '** Host ISOCHRONOUS Read (IN) test cases:'
|
/openbmc/linux/Documentation/process/ |
H A D | deprecated.rst | 63 cases is to refactor the code as suggested below to avoid the open-coded 129 is strscpy(), though care must be given to any cases where the return 144 strscpy(), though care must be given to any cases where the return value 147 errno when it truncates). Any cases still needing NUL-padding should 153 attribute to avoid future compiler warnings. For cases still needing 162 though care must be given to any cases where the return value of strlcpy() 202 The C language allows switch cases to fall through to the next case 222 cases, we have adopted a pseudo-keyword macro "fallthrough" which 242 for these cases. The older style of one-element or zero-length arrays should 350 There are two special cases of replacement where the DECLARE_FLEX_ARRAY() [all …]
|
/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/openbmc/poky/meta/lib/oeqa/core/tests/ |
H A D | test_loader.py | 47 cases = set(getSuiteCasesIDs(tc.suites)) 48 msg = 'Expected just %s cases' % ', '.join(expected_cases) 49 self.assertEqual(cases, expected_cases, msg=msg)
|