Searched refs:cases (Results 1 – 25 of 40) 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.
35 # Do not audit the cases where traced_perf attempts to access /proc/[pid] for39 # Do not audit failures to signal a process, as there are cases when this is
45 [==========] Running 11 tests from 2 test cases. 76 [==========] 11 tests from 2 test cases ran. (44495 ms total)
141 echo " $TEST_NAME failed for the following cases:\n\t"147 echo " $TEST_NAME passed for all cases!"
295 Case::Case(const string& c) { cases.push_back(c); } in Case()298 int N = this->cases.size(); in Write()301 string s = this->cases[i]; in Write()321 int N = this->cases.size(); in Write()323 this->cases[i]->Write(to); in Write()
207 transact_switch->cases.push_back(default_case); in finish()218 this->code_to_method_name_switch->cases.push_back(code_switch_default_case); in finish()539 stubClass->transact_switch->cases.push_back(c); in generate_stub_case()575 stubClass->transact_switch->cases.push_back(c); in generate_stub_case_outline()763 stubClass->code_to_method_name_switch->cases.push_back(c); in generate_methods()805 stubClass->transact_switch->cases.push_back(c); in generate_methods()815 stubClass->transact_switch->cases.push_back(c); in generate_methods()899 stub->transact_switch->cases.push_back(c); in generate_interface_descriptors()
274 std::vector<std::string> cases; member285 std::vector<std::shared_ptr<Case>> cases; member
35 // cases. Same as above, except dependent on system_current stubs.
39 : A process that loads and runs the actual test cases and use auto-generated42 framework and test cases are written in Python for fast iteration and easy debugging114 "TestClass:test_case_name", for multiple test cases, quote them using " and225 * Individual test directories: logs for individual test cases
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;
17 The intention is to cover the 80% use cases, not be all things to all users.
53 // error cases occurring.
9 * Readable syntax. Common cases should be concise, and pretty much anyone
26 - Parser code must explicitly handle these cases. Example:
20 * `--alignment-offset=N` - In some cases, the "super" partition is misaligned within its parent blo…
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