u wouldn't say [EMAIL PROTECTED]
No, you usually wouldn't (though you could). But if you had a @page
variable that represented just one Page, it would be quite sensible
and common to say @pages == [EMAIL PROTECTED]
That's really all that mock_page i
a generic
resource as a model, I'd consider wrapping it inside a model class and
spec'ing it out as a model.
--
Have Fun,
Steve Eley
Deep Salt Team
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
ication code in a spec, and
make sure that nothing you do in a spec leaves a permanent change in
memory. I can't know if that's your problem, of course, but it's
something to think about.
--
Have Fun,
Steve Eley
Deep Salt Team
___
rs
Because
>> you'll come back to this code in 6-12 months and be totally stuck
>> trying to figure out what is where.
>>
>> I recently wrote a viewpoint on this that might help you:
>>
>> http://www.lindsaar.net/2008/6/24/tip-24-being-clever-in-specs-is-for-dummies
>>
>> Hope you do well with Rspec, feel free to ask more questions!
>>
>> --
>> http://lindsaar.net/
>> Rails, RSpec, Puppet and Life blog
>> ___
>> rspec-users mailing list
>> rspec-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> ___
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
--
Have Fun,
Steve Eley
Deep Salt Team
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
rtually nothing in, so that only means changing
one or two lines of code each time. I don't consider that much of a
burden.
--
Have Fun,
Steve Eley
Deep Salt Team
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
ple to include it in their config.*
block if they want to use it?
--
Have Fun,
Steve Eley
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users