Lines Matching refs:our
100 object prophecy that our object should extend specific class, the second one says that
106 Ok, now we have our object prophecy. What can we do with it? First of all, we can get
107 our object *dummy* by revealing its prophecy:
128 awesome if we don't care about our _doubles_ (objects that reflect originals)
156 This promise will cause any call to our double's `read()` method with exactly one
212 optimal enough. We hardcoded `'everzet'` in our expectation. Isn't there a better
236 `ExactValueToken` is not very useful in our case as it forced us to hardcode the username.
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.
276 We've just described how our stub object should behave, even though the original object could have
315 Ok, now we know how to define our prophecy method promises, let's get our stub from
342 The `shouldBeCalled()` method here assigns `CallPrediction` to our method prophecy.