Searched refs:case (Results 1 – 25 of 494) sorted by relevance
12345678910>>...20
29 case ...:;@p34 case ...:...35 case ...:;@p40 case ...:...41 case ...:42 case ...:;@p
102 echo "<testcase name=\"$case\" time=\"0\">" >> $tmp_res_file105 echo -e "\e[91m$case FAILED\e[39m"112 echo -e "$case PASSED"
6 code writing for fatal and assert handler for error case testing. They can13 When writing error testing case (or we call it negative test case), we might61 If the expected error was caught, the test case will pass.92 test case, we do not recover it so far.105 Assert error expected as part of test case.109 case type is 0123 Fatal error expected as part of test case.124 case type is 1137 Fatal error expected as part of test case.138 case type is 2[all …]
98 case PM_DEVICE_ACTION_RESUME:104 case PM_DEVICE_ACTION_SUSPEND:110 case PM_DEVICE_ACTION_TURN_ON:114 case PM_DEVICE_ACTION_TURN_OFF:154 case PM_DEVICE_ACTION_SUSPEND:158 case PM_DEVICE_ACTION_RESUME:162 case PM_DEVICE_ACTION_TURN_ON:166 case PM_DEVICE_ACTION_TURN_OFF:
13 Matching is not case sensitive.22 Matching is not case sensitive.
13 int "Ticks to allow for fuzz case processing"19 following a unit-test style case, so the default is short to
1 This test case verifies that kernel fatal error handling works correctly
19 * Use `snake case`_ for code and variables.30 clarity, avoid emojis in any case.37 .. _snake case:
19 integration between the NS RTOS (Zephyr in this case) and the secure38 case).40 They also provide a useful test case to validate any PRs that make meaningful
1 This test case verifies that kernel fatal error logging message can be captured.
1 This test case verifies that kernel fatal error handling works correctly.
6 # so we only need to set link order linking in case a custom C library is linked
10 /* The async_api.nocache_mem_dt test case expects a non-cachable RAM region */
9 * address maybe zero(NULL) and break some test case assertions.
165 for case in self.testcases:166 if case.status == TwisterStatus.STARTED:167 case.status = TwisterStatus.FAIL168 elif case.status == TwisterStatus.NONE:169 case.status = status171 case.reason = reason173 case.reason = self.reason
468 for case in ts.testcases:469 testcases.append(case.name)478 for case in ts.testcases:479 testcases.append(case.detailed_name)482 for case in ts.testcases:483 testcases.append(case.detailed_name)488 for case in ts.testcases:489 if case.detailed_name in testcases:490 testcases.remove(case.detailed_name)678 case = instance.set_case_status_by_name([all …]
20 as the use case is known to be working on earlier commit or release.21 In this case, providing directly the guilty commit when submitting the bug
12 int "UART baudrate for DUT_AUX to test mismatch case"
16 this is acceptable or not will depend on the use case.
17 this is acceptable or not will depend on the use case.
47 Number of times to retry initialization commands in case of failure87 Number of times to retry sending command to SD card in case of failure93 Number of times to retry sending data to SD card in case of failure
12 A typical use case for a watchdog is that the board is restarted in case some piece of code
20 :kconfig:option:`CONFIG_NET_SAMPLE_PACKET_TXTIME` option. In this case the value is30 to create an ``AF_PACKET`` type socket. In this case, the ``echo-server``
20 * This use case is only applicable in PM_DEVICE mode.
23 significantly reduce memory footprint in case of application that does
