Conversation
Renamed MockMinder to Mock
|
You confused me when you wrote "I prefer the explicit declaration of the mock." You aren't saying that you don't like the implicit, are you? But it looks pretty good to me. I think we need to do a little more renaming to go along with it. In the mock definitions, minder is no longer a good alias. Not sure offhand if the generic "self" is appropriate or if there would be a better one. The mock attribute inside of Mock is confusing now. Maybe that should be named subject or something. On Jan 17, 2013, at 11:49 AM, David Corbin notifications@github.com wrote:
|
|
No. I meant I prefer to explicitly declare val that is the mock, and assign the minder invoking the implicit conversion. Not do foo.mock. On Jan 18, 2013, at 8:36 AM, Kiel Hodges notifications@github.com wrote:
|
Take a look. The conversion works fine in the real world cases. There was one not-real-world case in the sample where a test was calling the mock directly. You can still do that the way you had it (queue.mock.nextRequest), but I prefer the explicit declaration of the mock.