Lines Matching refs:call
89 The result of the `prophesize()` method call is a new object of class `ObjectProphecy`. Yes,
140 Oh wow. We've just made an arbitrary call on the object prophecy? Yes, we did. And this
141 call returned us a new object instance of class `MethodProphecy`. Yep, that's a specific
149 As a matter of fact, the call that we made earlier (`willReturn('value')`) is a simple
156 This promise will cause any call to our double's `read()` method with exactly one
160 - `ReturnPromise` or `->willReturn(1)` - returns a value from a method call
161 …eturnArgumentPromise` or `->willReturnArgument($index)` - returns the nth method argument from call
183 behaviors where some method call changes behavior of others. In PHPUnit or Mockery
218 wildcards. As a matter of fact, `->setName('everzet')` looks like a simple call just
325 (method call), Prophecy will force you to define all the communications - it throws
326 the `UnexpectedCallException` for any call you didn't describe with object prophecy before
344 of your doubles, Prophecy records every single call you're making against it inside your
356 check happen? Whenever you call `checkPredictions()` on the main Prophet object:
362 In PHPUnit, you would want to put this call into the `tearDown()` method. If no predictions
363 are defined, it would do nothing. So it won't harm to call it after every test.
379 section, Prophecy records every call made during the double's entire lifetime. This means