On Thu, Sep 24, 2009 at 8:13 PM, Eric Hahn wrote:
>
> The controllers themselves are using josevalim's wonderful
> inherited_resources gem, so they are incredibly small - I'm basically looking
> for something like this on the rspec side...
(*googling*) Aha. Looks a lot like the old make_resou
I'd like to DRY out my controller specs but am having difficulties doing so and
am hopeful that a more experienced rspec expert can shed some much-needed light
on my woes...
The controllers themselves are using josevalim's wonderful inherited_resources
gem, so they are incredibly small - I'm ba
I'd like to DRY out my controller specs but am having difficulties doing so and
am hopeful that a more experienced rspec expert can shed some much-needed light
on my woes...
The controllers themselves are using josevalim's wonderful inherited_resources
gem, so they are incredibly small - I'm ba
Hey, I'm having a bit of a Works For Me(tm) problem with my patch to rspec.
The idea of the patch is to allow specifying a non-default port for the
--drb option to connect to. I got the matching patches into Cucumber and
Spork already, and I would like to get this out in RSpec as well. It Works
On Thu, Sep 24, 2009 at 8:18 AM, Xavier To wrote:
> Hi,
>
> I just tried upgrading to ruby 1.9 and rspec has been giving me strange
> errors when I run them with "rake spec". I get for almost every test gives
> me a "can't modify frozen object"
>
> The other thing that confuses me is the fact that
Hi,
I just tried upgrading to ruby 1.9 and rspec has been giving me strange
errors when I run them with "rake spec". I get for almost every test gives
me a "can't modify frozen object"
The other thing that confuses me is the fact that running script/spec
spec/**/*.rb on the same project using rub
