Searched refs:cases (Results 1 – 25 of 32) sorted by relevance
12
5 * run_tests.sh: The main entry to run test cases. Using different6 test cases under testdata/*.
4 need special handling for some test cases as they are not applicable for the43 - `PTS_SmpFailureCase` enables handling for various SMP failure cases.
96 In nearly all cases, variables should be declared and initialized on the same line.226 // particular, edge cases, and whether a pointer argument may or may not be
45 [==========] Running 11 tests from 2 test cases. 76 [==========] 11 tests from 2 test cases ran. (44495 ms total)
129 echo " $TEST_NAME failed for the following cases:\n\t"135 echo " $TEST_NAME passed for all cases!"
320 Case::Case(const string& c) { cases.push_back(c); } in Case()323 int N = this->cases.size(); in Write()326 string s = this->cases[i]; in Write()346 int N = this->cases.size(); in Write()348 this->cases[i]->Write(to); in Write()
209 transact_switch->cases.push_back(default_case); in finish()220 this->code_to_method_name_switch->cases.push_back(code_switch_default_case); in finish()551 stubClass->transact_switch->cases.push_back(c); in generate_stub_case()588 stubClass->transact_switch->cases.push_back(c); in generate_stub_case_outline()770 stubClass->code_to_method_name_switch->cases.push_back(c); in generate_methods()806 stubClass->transact_switch->cases.push_back(c); in generate_methods()856 stub->transact_switch->cases.push_back(c); in generate_interface_descriptors()
278 std::vector<std::string> cases; member289 std::vector<Case*> cases; member
35 // cases. Same as above, except dependent on system_current stubs.
11 # perfevents problems in cases where CPU goes on/off during measurement;
50 # which is super useful in some cases.
14 # perfevents problems in cases where CPU goes on/off during measurement;
53 // error cases occurring.
20 * `--alignment-offset=N` - In some cases, the "super" partition is misaligned within its parent blo…
26 - Parser code must explicitly handle these cases. Example:
34 tests to Fuzzy Fastboot. However, in most cases the optional device specific53 many more additional tests cases.317 In most cases this message at the bottom is all that is needed to figure out why it failed.353 oem commands all have provided test cases. Be sure to test both the positive case
356 const Type * const *cases; member
107 client to make other requests. But in certain cases, an OKAY will even
128 4) Run non-CTS test cases:
145 these cases.