| /external/autotest/client/site_tests/security_RootfsStatefulSymlinks/ |
| D | security_RootfsStatefulSymlinks.py | 30 def validate_attributes(self, link, expectations): argument
37 if destination != expectations['destination']:
40 link, expectations['destination'], destination)
50 return expectations['can_dangle']
57 if (owner == expectations['owner'] and
58 group == expectations['group'] and
59 mode == expectations['mode']):
63 destination, expectations['owner'],
64 expectations['group'], expectations['mode'],
|
| /external/autotest/server/site_tests/network_WiFi_RegDomain/ |
| D | control | 42 # TODO(quiche): Add ath9k expectations for channels 52 and 120.
45 # This first set of expectations is based on
55 # Many of the 'passive-scan' expectations for the remaining
57 # least, not all of the passive scanning expectations can be
112 # TODO(quiche): Add wp2 expectations for channels 52 and 120. If
113 # those expectations match the (to-be-added) expectations for
122 # Many of the 'passive-scan' expectations seem to follow from
124 # the passive scanning expectations can be attributed to
126 # investigated if the 'passive-scan' expectations are due to
|
| /external/skia/tools/skpbench/ |
| D | _hardware.py | 90 def check_all(expectations, stringvalues): argument
91 if len(stringvalues) != len(expectations):
94 (len(expectations), '\n'.join(stringvalues)))
96 for value, expected in zip(stringvalues, expectations):
|
| D | _hardware_pixel_c.py | 98 expectations = \
111 Expectation.check_all(expectations, result.splitlines())
|
| D | _hardware_nexus_6p.py | 138 expectations = \
150 Expectation.check_all(expectations, result.splitlines())
|
| /external/skia/bench/ |
| D | check_bench_regressions.py | 108 def read_expectations(expectations, filename): argument
118 if bench_entry in expectations:
122 expectations[bench_entry] = (float(elements[LB_IDX]),
126 def check_expectations(lines, expectations, key_suffix): argument
157 if bench_platform_key not in expectations:
160 this_min, this_max, this_expected = expectations[bench_platform_key]
|
| /external/libyuv/files/tools_libyuv/autoroller/unittests/ |
| D | roll_deps_test.py | 50 self.expectations = []
54 self.expectations.append((args, kwargs, returns))
57 if not self.expectations:
59 exp_args, exp_kwargs, exp_returns = self.expectations.pop(0)
82 self.assertEqual(self.fake.expectations, [])
|
| /external/webrtc/talk/app/webrtc/java/testcommon/src/org/webrtc/ |
| D | PeerConnectionTest.java | 745 PeerConnection pc, ObserverExpectations expectations) {
746 expectations.dataChannel.unregisterObserver();
747 expectations.dataChannel.dispose();
748 expectations.expectStatsCallback();
749 assertTrue(pc.getStats(expectations, null));
750 assertTrue(expectations.waitForAllExpectationsToBeSatisfied(TIMEOUT_SECONDS));
751 expectations.expectIceConnectionChange(IceConnectionState.CLOSED);
752 expectations.expectSignalingChange(SignalingState.CLOSED);
754 assertTrue(expectations.waitForAllExpectationsToBeSatisfied(TIMEOUT_SECONDS));
755 expectations.expectStatsCallback();
[all …]
|
| /external/skia/tests/ |
| D | GrShapeTest.cpp | 273 void testExpectations(skiatest::Reporter* reporter, SelfExpectations expectations) const;
416 void TestCase::testExpectations(skiatest::Reporter* reporter, SelfExpectations expectations) const { in testExpectations()
419 if (expectations.fPEHasEffect) { in testExpectations()
421 REPORTER_ASSERT(reporter, expectations.fPEHasValidKey == SkToBool(fAppliedPEKey.count())); in testExpectations()
423 REPORTER_ASSERT(reporter, expectations.fPEHasValidKey == SkToBool(fAppliedFullKey.count())); in testExpectations()
424 if (expectations.fStrokeApplies && expectations.fPEHasValidKey) { in testExpectations()
434 if (expectations.fStrokeApplies) { in testExpectations()
616 TestCase::SelfExpectations expectations; in test_basic() local
620 expectations.fPEHasEffect = false; in test_basic()
621 expectations.fPEHasValidKey = false; in test_basic()
[all …]
|
| D | PDFMetadataAttributeTest.cpp | 33 static const char* expectations[] = { in DEF_TEST() local
44 for (const char* expectation : expectations) { in DEF_TEST()
|
| /external/autotest/client/site_tests/graphics_dEQP/scripts/ |
| D | failure_matrix.py | 55 expectations = {}
58 expectations[key] = set(data[key])
59 return expectations
|
| D | process_logs.py | 115 expectations = {}
118 expectations[key] = set(data[key])
119 return expectations
|
| /external/v8/tools/release/ |
| D | test_scripts.py | 806 expectations = []
808 expectations.append(Cmd("which vi", "/usr/bin/vi"))
809 expectations += [
830 expectations.append(RL("")) # Open editor.
832 expectations.append(
834 expectations += [
848 expectations.append(RL("Y")) # Sanity check.
849 expectations += [
869 self.Expect(expectations)
947 expectations = [
[all …]
|
| /external/googletest/googlemock/docs/v1_5/ |
| D | CheatSheet.md | 79 1. Set your expectations on the mock objects (How will they be called? What wil they do?).
81 …1. When a mock objects is destructed, Google Mock automatically verifies that all expectations on …
97 // ... other expectations ...
126 `EXPECT_CALL()` sets **expectations** on a mock method (How will it be
133 .After(expectations) *
410 By default, the expectations can be matched in _any_ order. If some
411 or all expectations must be matched in a given order, there are two
450 When you have a long chain of sequential expectations, it's easier to
473 To put many expectations in a sequence conveniently:
490 Google Mock will verify the expectations on a mock object when it is destructed, or you can do it e…
[all …]
|
| 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…
201 …successfully is to set the _right expectations_ on it. If you set the expectations too strict, you…
230 **Note:** Why do we use a macro to do this? It serves two purposes: first it makes expectations eas…
329 …ave a single expectation. More realistically, you're going to specify expectations on multiple moc…
331 By default, when a mock method is invoked, Google Mock will search the expectations in the **revers…
342 …expectations? The reason is that this allows a user to set up the default expectations in a mock o…
[all …]
|
| D | FrequentlyAskedQuestions.md | 308 ## I can't figure out why Google Mock thinks my expectations are not satisfied. What should I do? …
313 you'll gain insights on why the expectations you set are not met.
325 (the mock function arguments, the state of relevant expectations, and
328 expectations.
370 ## The "newer expectations override older ones" rule makes writing expectations awkward. Why does …
376 // 2 the second time. However, I have to write the expectations in the
389 By default, expectations don't have to be matched in _any_ particular
396 put the expectations in sequence:
400 // 2 the second time. Using a sequence, we can write the expectations
425 expectations (and `ON_CALL`s) from back to front? Because this
[all …]
|
| /external/googletest/googlemock/docs/ |
| 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…
201 …successfully is to set the _right expectations_ on it. If you set the expectations too strict, you…
230 **Note:** Why do we use a macro to do this? It serves two purposes: first it makes expectations eas…
329 …ave a single expectation. More realistically, you're going to specify expectations on multiple moc…
331 By default, when a mock method is invoked, Google Mock will search the expectations in the **revers…
342 …expectations? The reason is that this allows a user to set up the default expectations in a mock o…
[all …]
|
| D | FrequentlyAskedQuestions.md | 312 ## I can't figure out why Google Mock thinks my expectations are not satisfied. What should I do? …
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
[all …]
|
| D | CheatSheet.md | 79 1. Set your expectations on the mock objects (How will they be called? What wil they do?).
81 …1. When a mock objects is destructed, Google Mock automatically verifies that all expectations on …
97 // ... other expectations ...
131 `EXPECT_CALL()` sets **expectations** on a mock method (How will it be
138 .After(expectations) *
447 By default, the expectations can be matched in _any_ order. If some
448 or all expectations must be matched in a given order, there are two
487 When you have a long chain of sequential expectations, it's easier to
510 To put many expectations in a sequence conveniently:
527 Google Mock will verify the expectations on a mock object when it is destructed, or you can do it e…
[all …]
|
| /external/googletest/googlemock/docs/v1_7/ |
| 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…
201 …successfully is to set the _right expectations_ on it. If you set the expectations too strict, you…
230 **Note:** Why do we use a macro to do this? It serves two purposes: first it makes expectations eas…
329 …ave a single expectation. More realistically, you're going to specify expectations on multiple moc…
331 By default, when a mock method is invoked, Google Mock will search the expectations in the **revers…
342 …expectations? The reason is that this allows a user to set up the default expectations in a mock o…
[all …]
|
| D | FrequentlyAskedQuestions.md | 312 ## I can't figure out why Google Mock thinks my expectations are not satisfied. What should I do? …
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
[all …]
|
| /external/googletest/googlemock/docs/v1_6/ |
| 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…
201 …successfully is to set the _right expectations_ on it. If you set the expectations too strict, you…
230 **Note:** Why do we use a macro to do this? It serves two purposes: first it makes expectations eas…
329 …ave a single expectation. More realistically, you're going to specify expectations on multiple moc…
331 By default, when a mock method is invoked, Google Mock will search the expectations in the **revers…
342 …expectations? The reason is that this allows a user to set up the default expectations in a mock o…
[all …]
|
| D | CheatSheet.md | 79 1. Set your expectations on the mock objects (How will they be called? What wil they do?).
81 …1. When a mock objects is destructed, Google Mock automatically verifies that all expectations on …
97 // ... other expectations ...
126 `EXPECT_CALL()` sets **expectations** on a mock method (How will it be
133 .After(expectations) *
419 By default, the expectations can be matched in _any_ order. If some
420 or all expectations must be matched in a given order, there are two
459 When you have a long chain of sequential expectations, it's easier to
482 To put many expectations in a sequence conveniently:
499 Google Mock will verify the expectations on a mock object when it is destructed, or you can do it e…
[all …]
|
| D | FrequentlyAskedQuestions.md | 312 ## I can't figure out why Google Mock thinks my expectations are not satisfied. What should I do? …
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
[all …]
|
| /external/python/cpython2/Lib/test/ |
| D | test_strftime.py | 89 expectations = (
116 for e in expectations:
|