Lines Matching refs:in

71 First of all, in Prophecy every word has a logical meaning, even the name of the library
91 in the near future. But first, you need to specify which object you're talking about,
101 it should implement some interface. Obviously, objects in PHP can implement multiple
121 assigned to `$prophecy` variable and in order to manipulate with your expectations, you
132 but when put in specific environment, behaves in specific way. Ok, I know, it's cryptic,
134 method signature does different things (has logic). To create stubs in Prophecy:
143 promises or predictions. We'll talk about method predictions later in the _Mocks_ section.
147 Promises are logical blocks, that represent your fictional methods in prophecy terms
165 Keep in mind, that you can always add even more promises by implementing
206 And now it doesn't matter how many times or in which order your methods are called.
212 optimal enough. We hardcoded `'everzet'` in our expectation. Isn't there a better
217 like simple method arguments, in reality they are not. They are argument token
236 `ExactValueToken` is not very useful in our case as it forced us to hardcode the username.
279 One last bit about arguments now. You might ask, what happens in case of:
308 promise that has the highest score. In this case, `Argument::type()` in case of success
333 are called mocks and in Prophecy they look almost exactly the same as stubs, except that
378 The last bit of awesomeness in Prophecy is out-of-the-box spies support. As I said in the previous
380 you don't need to record predictions in order to check them. You can also do it