Lines Matching refs:with

8 enough to be used inside any testing framework out there with minimal effort.
61 Then simply install it with composer:
72 itself (Prophecy). When you start feeling that, you'll become very fluid with this
76 behavior of objects with very limited knowledge about them. But as with any other prophecy,
106 Ok, now we have our object prophecy. What can we do with it? First of all, we can get
121 assigned to `$prophecy` variable and in order to manipulate with your expectations, you
122 should work with it. `$dummy` is a dummy - a simple php object that tries to fulfil your
133 but bear with me for a minute. Simply put, a stub is a dummy, which depending on the called
142 method with arguments prophecy. Method prophecies give you the ability to create method
156 This promise will cause any call to our double's `read()` method with exactly one
171 predictions for the same method calls with the same arguments. This means:
227 with your expectations. And yes, those classnames are damn big. That's why there's a
237 That's why Prophecy comes bundled with a bunch of other tokens:
250 And you can add even more by implementing `TokenInterface` with your own custom classes.
252 So, let's refactor our initial `{set,get}Name()` logic with argument tokens:
275 That's it. Now our `{set,get}Name()` prophecy will work with any string argument provided to it.
322 As you might see, the only difference between how we get dummies and stubs is that with
323 stubs we describe every object conversation instead of just agreeing with `null` returns
326 the `UnexpectedCallException` for any call you didn't describe with object prophecy before
331 Now we know how to define doubles without behavior (dummies) and doubles with behavior, but
365 There are plenty more predictions you can play with:
391 Such manipulation with doubles is called spying. And with Prophecy it just works.