On Thu, Feb 24, 2011 at 11:08 PM, David Chelimsky wrote:
> largely due to changes in Rails 3, not just changes in RSpec.
>
> The good news is that the rspec-rails-2 gem has significantly less monkey
> patching than the rspec-rails-1 gems did, so the likelihood that future Rails
> releases will f
Craig Demyanovich wrote in post #983991:
> On Fri, Feb 25, 2011 at 4:30 PM, Radhesh Kamath
> wrote:
>
>> Which version of rspec-rails should I use for Rails 2.3.8?
>
>
> rspec-rails 1.3.3 is currently the latest release for Rails 2.3.x.
>
I am getting this error with my current setup, which I thin
On Fri, Feb 25, 2011 at 2:30 PM, Radhesh Kamath wrote:
> Hi experts,
>
> I picked up a copy of the rspec book and wrote some tests in spec/lib
> and spec/models for my Rails 2.3.8 code.
>
> I was using rspec 2.5.1, rspec-core 2.5.0, rspec-expectations 2.5.0 et.
> al.
>
> But I realised that the rs
On Fri, Feb 25, 2011 at 4:30 PM, Radhesh Kamath wrote:
> Which version of rspec-rails should I use for Rails 2.3.8?
rspec-rails 1.3.3 is currently the latest release for Rails 2.3.x.
Regards,
Craig
___
rspec-users mailing list
rspec-users@rubyforge.or
Hi experts,
I picked up a copy of the rspec book and wrote some tests in spec/lib
and spec/models for my Rails 2.3.8 code.
I was using rspec 2.5.1, rspec-core 2.5.0, rspec-expectations 2.5.0 et.
al.
But I realised that the rspec-rails version I am using is meant for
Rails3.
Which version of rsp
Thanks for all of your insight guys.
As it turned out the culprit was
".any_instance.stubs(:valid?).returns(false)" which was being run in
the controllers.
I changed some things around any now everything is working as
expected.
I was using the following:
Rails 3.0.0
RSpec 2.4.0
RSpec Rails 2.4.1
