On 2008-09-05, at 18:22, Jonathan Linowes wrote:
On Sep 5, 2008, at 5:44 PM, Nick Hoffman wrote:
Property.stub!(:find).and_return mock_property1, mock_property2
try
Property.stub!(:find).and_return( [mock_property1, mock_property2] )
Thanks Jonathan and David. That was a silly mistake.
With that fixed, a new question has popped up. My specs for the method
I previously mentioned are now:
185 describe '#add_properties' do # {{{
186 it 'should add properties to the map' do
187 map = RentalMap.new @map_name, @latitude,
@longitude
188 mock_property1 = mock 'property'
189 mock_property2 = mock 'property'
190 marker1_contents = 'Some contents for the first property'
191 marker2_contents = 'Some contents for the second property'
192
193 Property.stub!(:find).and_return [mock_property1,
mock_property2]
194 map.stub!(:add_marker).and_return "Doesn't matter"
195
196 mock_property1.stub!(:address ).and_return '400 Bloor Street'
197 mock_property1.stub!(:latitude ).and_return 12.34
198 mock_property1.stub!(:longitude).and_return 56.78
199 mock_property2.stub!(:address ).and_return '500 Bloor Street'
200 mock_property2.stub!(:latitude ).and_return 12.45
201 mock_property2.stub!(:longitude).and_return 56.89
202 map.stub!(:generate_marker_contents).twice.and_return
marker1_contents, marker2_contents
203
204 map.should_receive(:add_marker).with mock_property1.address,
mock_property1.latitude, mock_property1.longitude, marker1_contents
205 map.should_receive(:add_marker).with mock_property2.address,
mock_property2.latitude, mock_property2.longitude, marker2_contents
206
207 map.add_properties
208 end
209 end # }}}
However, lines 190 and 191 feel a bit like I'm setting up fixture
data. But the only alternative that I can think of will fail:
-Comment out lines 190 and 191.
-On line 202, replace "marker*_contents" with the strings on lines 190
and 191.
-Lines 204 and 205 will have to call #generate_marker_contents for the
last argument.
-Lines 204 and 205 will then consume the two calls to
#generate_marker_contents that I expect on line 202.
Can anyone suggest a better/different way of doing this?
Thanks,
Nick
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
