Home
last modified time | relevance | path

Searched refs:expectations (Results 1 – 25 of 45) sorted by relevance

12

/src/contrib/libcbor/test/
H A Dtest_allocator.c12 call_expectation *expectations; variable
19 expectations = calloc(calls, sizeof(expectations)); in set_mock_malloc()
22 expectations[i] = va_arg(args, call_expectation); in set_mock_malloc()
29 free(expectations); in finalize_mock_malloc()
50 if (expectations[alloc_calls] == MALLOC) { in instrumented_malloc()
53 } else if (expectations[alloc_calls] == MALLOC_FAIL) { in instrumented_malloc()
62 alloc_calls < alloc_calls_expected ? expectations[alloc_calls] : -1); in instrumented_malloc()
73 if (expectations[alloc_calls] == REALLOC) { in instrumented_realloc()
76 } else if (expectations[alloc_calls] == REALLOC_FAIL) { in instrumented_realloc()
85 alloc_calls < alloc_calls_expected ? expectations[alloc_calls] : -1); in instrumented_realloc()
/src/contrib/googletest/googlemock/src/
H A Dgmock-spec-builders.cc117 ::std::vector<ExpectationBase*> expectations(1, this); in RetireAllPreRequisites()
118 while (!expectations.empty()) { in RetireAllPreRequisites()
119 ExpectationBase* exp = expectations.back(); in RetireAllPreRequisites()
120 expectations.pop_back(); in RetireAllPreRequisites()
128 expectations.push_back(next); in RetireAllPreRequisites()
139 ::std::vector<const ExpectationBase*> expectations(1, this); in AllPrerequisitesAreSatisfied()
140 while (!expectations.empty()) { in AllPrerequisitesAreSatisfied()
141 const ExpectationBase* exp = expectations.back(); in AllPrerequisitesAreSatisfied()
142 expectations.pop_back(); in AllPrerequisitesAreSatisfied()
149 expectations.push_back(next); in AllPrerequisitesAreSatisfied()
[all …]
/src/contrib/googletest/docs/
H A Dgmock_cheat_sheet.md102 4. Set your expectations on the mock objects (How will they be called? What
107 expectations on it have been satisfied.
124 // ... other expectations ...
186 By default, expectations can be matched in *any* order. If some or all
187 expectations must be matched in a given order, you can use the
194 gMock will verify the expectations on a mock object when it is destructed, or
200 // Verifies and removes the expectations on mock_obj;
204 // Verifies and removes the expectations on mock_obj;
210 Do not set new expectations after verifying and clearing a mock after its use.
211 Setting expectations after code that exercises the mock has undefined behavior.
H A Dgmock_faq.md82 ### I can't figure out why gMock thinks my expectations are not satisfied. What should I do?
86 trace, you'll gain insights on why the expectations you set are not met.
101 intercepts these messages and finds that they don't match any expectations, it
104 You can learn to ignore the errors, or you can rewrite your expectations to make
128 arguments, the state of relevant expectations, and etc) to help the user debug.
130 state of relevant expectations.
170 ### The "newer expectations override older ones" rule makes writing expectations awkward. Why does …
178 // 2 the second time. However, I have to write the expectations in the
191 By default, expectations don't have to be matched in *any* particular order. If
197 expectations in sequence:
[all …]
H A Dgmock_for_dummies.md19 * **Mocks** are objects pre-programmed with *expectations*, which form a
35 2. next, you create some mock objects and specify its expectations and behavior
38 violation to the expectations as soon as it arises.
215 3. Specify your expectations on them (How many times will a method be called?
221 expectations on it have been satisfied.
266 **Important note:** gMock requires expectations to be set **before** the mock
269 any expectations on a mock after passing the mock to an API.
283 The key to using a mock object successfully is to set the *right expectations*
284 on it. If you set the expectations too strict, your test will fail as the result
342 it makes expectations easily identifiable (either by `grep` or by a human
[all …]
H A Dgmock_cook_book.md247 .. set more expectations on mock_stream ...
463 *methods* with no expectations); they do not affect *unexpected* calls (calls of
464 methods with expectations, but they don't match). See
651 Now you want to mock this interface such that you can set expectations on it.
1691 If you would rather have all calls occur in the order of the expectations, put
1728 require you to come up with different names for the expectations in the chains.
1737 So, to specify the partial order on the expectations we need to do two things:
1774 When a mock method is called, gMock only considers expectations that are still
2698 In the example above, we set our normal gMock expectations, but then add an
2770 First let’s see how we can set expectations on the `MakeBuzz()` method, which
[all …]
/src/tools/regression/poll/
H A DReadme10 expectations; state 0 fails in FreeBSD-4 so the above is wrong
15 l: Linux-2.6.10 with old tests (only state 0 has different expectations)
/src/contrib/googletest/docs/reference/
H A Dmocking.md62 Creates an [expectation](../gmock_for_dummies.md#setting-expectations) that the
83 .After(expectations...) // Can be used any number of times
158 the expectations are declared.
182 `.After(`*`expectations...`*`)`
187 The parameter *`expectations...`* can be up to five
189 The mock function call is expected to occur after all of the given expectations.
211 // Collect all expectations of InitElement() calls
294 The `RetiresOnSaturation` clause is only meaningful for expectations with an
327 *Does not* set any expectations that the method will be called.
530 Represents a chronological sequence of expectations. See the
[all …]
/src/crypto/openssl/test/
H A DREADME.ssltest.md45 to succeed. All configured test expectations are verified against the second
61 ### Test expectations
72 `close_notify`). Warning alert expectations are not yet supported. (A warning
93 * ExpectedNPNProtocol, ExpectedALPNProtocol - NPN and ALPN expectations.
273 Note that the test expectations sometimes depend on the Configure settings. For
275 protocols: a build with `enable-ssl3` has different test expectations than a
/src/contrib/atf/atf-sh/
H A Dlibatf-sh.subr157 # 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'.
/src/contrib/googletest/googlemock/test/
H A Dgmock_output_test_golden.txt97 Google Mock tried the following 2 expectations, but none matched:
119 Google Mock tried the following 2 expectations, but none matched:
141 Google Mock tried the following 2 expectations, but none matched:
335 …verified when the object is destructed. Leaking a mock means that its expectations aren't verified…
/src/contrib/googletest/googlemock/
H A DREADME.md24 - Does automatic verification of expectations (no record-and-replay needed).
/src/crypto/openssl/doc/man3/
H A DOSSL_STORE_expect.pod24 By default, no expectations on the types of objects to be loaded are made.
H A DBIO_f_base64.pod57 For reading, it removes all expectations on newlines in the input data.
H A DOSSL_HTTP_REQ_CTX.pod96 OSSL_HTTP_REQ_CTX_set_expected() optionally sets in I<rctx> some expectations
H A DOSSL_HTTP_transfer.pod169 and expectations on the response using the following parameters.
/src/sys/contrib/device-tree/Bindings/soc/qcom/
H A Dqcom,glink.txt58 meet expectations of the remote.
/src/contrib/libxo/doc/
H A Dencoders.rst61 differences in CSV file consumers and their expectations. The CSV
63 expectations.
/src/contrib/mandoc/
H A DINSTALL165 check that no "#define HAVE_*" differ from your expectations.
/src/crypto/openssl/doc/man7/
H A Dprovider-mac.pod132 The same expectations apply to I<outsize> as documented for
H A Dprovider-cipher.pod201 The same expectations apply to I<outsize> as documented for
/src/crypto/heimdal/lib/krb5/
H A Dkrb5_err.et146 error_code KRB5_KDCREP_MODIFIED, "KDC reply did not match expectations"
/src/crypto/openssl/doc/designs/quic-design/
H A Ddgram-api.md270 to code more realistic performance expectations since it
295 code a clear way to determine if its expectations are met.
/src/sys/dev/isp/
H A DHardware.txt15 it'll differ from your expectations.
/src/crypto/krb5/src/lib/krb5/error_tables/
H A Dkrb5_err.et200 error_code KRB5_KDCREP_MODIFIED, "KDC reply did not match expectations"

12