| /freebsd-13.1/contrib/libcbor/test/ |
| H A D | memory_allocation_test.c | 34 call_expectation *expectations; variable 41 expectations = calloc(calls, sizeof(expectations)); in set_mock_malloc() 44 expectations[i] = va_arg(args, call_expectation); in set_mock_malloc() 51 free(expectations); in finalize_mock_malloc() 59 if (expectations[alloc_calls] == MALLOC) { in instrumented_malloc() 62 } else if (expectations[alloc_calls] == MALLOC_FAIL) { in instrumented_malloc() 78 if (expectations[alloc_calls] == REALLOC) { in instrumented_realloc() 81 } else if (expectations[alloc_calls] == REALLOC_FAIL) { in instrumented_realloc()
|
| /freebsd-13.1/contrib/googletest/googlemock/src/ |
| H A D | gmock-spec-builders.cc | 112 while (!expectations.empty()) { in RetireAllPreRequisites() 113 ExpectationBase* exp = expectations.back(); in RetireAllPreRequisites() 114 expectations.pop_back(); in RetireAllPreRequisites() 122 expectations.push_back(next); in RetireAllPreRequisites() 134 while (!expectations.empty()) { in AllPrerequisitesAreSatisfied() 135 const ExpectationBase* exp = expectations.back(); in AllPrerequisitesAreSatisfied() 136 expectations.pop_back(); in AllPrerequisitesAreSatisfied() 143 expectations.push_back(next); in AllPrerequisitesAreSatisfied() 154 while (!expectations.empty()) { in FindUnsatisfiedPrerequisites() 156 expectations.pop_back(); in FindUnsatisfiedPrerequisites() [all …]
|
| /freebsd-13.1/tools/regression/poll/ |
| H A D | Readme | 11 expectations; state 0 fails in FreeBSD-4 so the above is wrong 16 l: Linux-2.6.10 with old tests (only state 0 has different expectations)
|
| /freebsd-13.1/contrib/googletest/googlemock/docs/ |
| H A D | ForDummies.md | 20 1. Create some mock objects and specify its expectations and behavior using an intuitive syntax; 21 …at uses the mock objects. Google Mock will catch any violation of the expectations as soon as it a… 122 …1. Specify your expectations on them (How many times will a method be called? With what arguments?… 124 …1. When a mock is destructed, Google Mock will automatically check whether all expectations on it … 165 **Important note:** Google Mock requires expectations to be set **before** the mock functions are c… 231 **Note:** Why do we use a macro to do this? It serves two purposes: first it makes expectations eas… 334 …ave a single expectation. More realistically, you're going to specify expectations on multiple moc… 348 …expectations? The reason is that this allows a user to set up the default expectations in a mock o… 351 …tisfied. In other words, the calls don't have to occur in the order the expectations are specified. 371 By creating an object of type `InSequence`, all expectations in its scope are put into a _sequence_… [all …]
|
| H A D | FrequentlyAskedQuestions.md | 317 you'll gain insights on why the expectations you set are not met. 329 (the mock function arguments, the state of relevant expectations, and 332 expectations. 374 ## The "newer expectations override older ones" rule makes writing expectations awkward. Why does … 380 // 2 the second time. However, I have to write the expectations in the 393 By default, expectations don't have to be matched in _any_ particular 400 put the expectations in sequence: 404 // 2 the second time. Using a sequence, we can write the expectations 429 expectations (and `ON_CALL`s) from back to front? Because this 444 test to test. Then in the test body they set the expectations, which [all …]
|
| H A D | CheatSheet.md | 79 1. Set your expectations on the mock objects (How will they be called? What wil they do?). 97 // ... other expectations ... 131 `EXPECT_CALL()` sets **expectations** on a mock method (How will it be 138 .After(expectations) * 449 By default, the expectations can be matched in _any_ order. If some 450 or all expectations must be matched in a given order, there are two 489 When you have a long chain of sequential expectations, it's easier to 512 To put many expectations in a sequence conveniently: 529 Google Mock will verify the expectations on a mock object when it is destructed, or you can do it e… 533 // Verifies and removes the expectations on mock_obj; [all …]
|
| H A D | CookBook.md | 182 .. set more expectations on mock_stream ... 427 Now you want to mock this interface such that you can set expectations 1398 different names for the expectations in the chains. Here's how it 2408 expectations). What's more, mock methods with different signatures 2469 verify that all expectations on it have been satisfied, and will 2493 // ... other expectations ... 2500 // this will verify the expectations anyway. 2523 set fresh expectations on it. 2535 expectations in sequences and insert calls to a dummy "check-point" 2660 If you violate the rules (for example, if you set expectations on a [all …]
|
| /freebsd-13.1/contrib/atf/atf-sh/ |
| H A D | libatf-sh.subr | 157 # Sets the expectations to 'death'. 170 # Sets the expectations to 'timeout'. 183 # Sets the expectations to 'exit'. 202 # Sets the expectations to 'fail'. 215 # Sets the expectations to 'pass'. 228 # Sets the expectations to 'signal'.
|
| /freebsd-13.1/contrib/googletest/googlemock/test/ |
| H A D | gmock_output_test_golden.txt | 93 Google Mock tried the following 2 expectations, but none matched: 114 Google Mock tried the following 2 expectations, but none matched: 135 Google Mock tried the following 2 expectations, but none matched: 317 …verified when the object is destructed. Leaking a mock means that its expectations aren't verified…
|
| /freebsd-13.1/sys/contrib/device-tree/Bindings/soc/qcom/ |
| H A D | qcom,glink.txt | 58 meet expectations of the remote.
|
| /freebsd-13.1/contrib/libxo/doc/ |
| H A D | encoders.rst | 61 differences in CSV file consumers and their expectations. The CSV 63 expectations.
|
| H A D | api.rst | 741 style and usage expectations::
|
| /freebsd-13.1/contrib/googletest/googlemock/ |
| H A D | README.md | 22 * handles unordered, partially ordered, or completely ordered expectations. 35 * Does automatic verification of expectations (no record-and-replay needed).
|
| /freebsd-13.1/contrib/mandoc/ |
| H A D | INSTALL | 160 check that no "#define HAVE_*" differ from your expectations.
|
| /freebsd-13.1/crypto/heimdal/lib/krb5/ |
| H A D | krb5_err.et | 146 error_code KRB5_KDCREP_MODIFIED, "KDC reply did not match expectations"
|
| /freebsd-13.1/sys/dev/isp/ |
| H A D | Hardware.txt | 16 it'll differ from your expectations.
|
| /freebsd-13.1/contrib/bc/manuals/ |
| H A D | build.md | 582 that this bc and dc will conform to the expectations of the user on each
|
| /freebsd-13.1/tools/test/testfloat/ |
| H A D | testfloat.txt | 738 tininess is detected after rounding. TestFloat alters its expectations
|
| /freebsd-13.1/contrib/openpam/ |
| H A D | aclocal.m4 | 531 # by default if the 'rm' program in use doesn't match our expectations; the
|
| /freebsd-13.1/contrib/file/ |
| H A D | aclocal.m4 | 531 # by default if the 'rm' program in use doesn't match our expectations; the
|
| /freebsd-13.1/contrib/ntp/sntp/libevent/ |
| H A D | aclocal.m4 | 541 # by default if the 'rm' program in use doesn't match our expectations; the
|
| /freebsd-13.1/contrib/libevent/ |
| H A D | aclocal.m4 | 541 # by default if the 'rm' program in use doesn't match our expectations; the
|
| /freebsd-13.1/contrib/openbsm/ |
| H A D | aclocal.m4 | 541 # by default if the 'rm' program in use doesn't match our expectations; the
|
| /freebsd-13.1/contrib/ntp/sntp/ |
| H A D | aclocal.m4 | 715 # by default if the 'rm' program in use doesn't match our expectations; the
|
| /freebsd-13.1/contrib/ntp/ |
| H A D | aclocal.m4 | 715 # by default if the 'rm' program in use doesn't match our expectations; the
|