[rspec-users] cucumber - when to stub/mock
Matthew Van Horn
mattvanhorn at gmail.com
Tue May 5 14:43:23 EDT 2009
Actually, I do have my own object wrapping GeoIp, and I stubbed the
method on that object that returns a country code for me.
I can see maybe creating another object to be used in the test
environment, but I can't see what advantages that offers over using
the rspec mocking framework.
On May 5, 2009, at 12:34 PM, Pat Maddox wrote:
> Don't mock the Geolp library directly. Wrap it with an API that fits
> your domain better. Then write a very simple object that implements
> the same API but doesn't hit the network. You can use a switch
> somewhere in env.rb to use your fake implementation or the Geolp one.
> On Sunday, May 3, 2009, Matthew Van Horn <mattvanhorn at gmail.com>
>> I'm just curious about this, since my solution involved stubbing a
>> call to GeoIp.
>> Is there a good rule of thumb for when you make exceptions to the
>> 'no stubbing' philosophy of Cucumber?
>> My step was: "Given I am accessing the site from Japan," but I can
>> think of other situations - mostly when interacting with web
>> services, that I'd probably want to stub something, rather than
>> requiring a net connection for testing.
>> thanks for any advice,
>> Matt Van Horn
>> rspec-users mailing list
>> rspec-users at rubyforge.org
> rspec-users mailing list
> rspec-users at rubyforge.org
More information about the rspec-users