On Jul 30, 2010, at 6:52 AM, Amit Jain wrote:

> David Chelimsky wrote:
>> On Jul 30, 2010, at 2:03 AM, Amit Jain wrote:
>> 
>>>> rails. Please do this:
>>>> it using some means other than what is recommended by Rails, which is to 
>>>> David
>>> (NameError)
>>> /home/Amit/Myworkspace/MyApplication/vendor/rails/activesupport/lib/active_support/dependencies.rb:158:in
>>>  
>>>  ... 11 levels...
>>> from /usr/lib/ruby/gems/1.8/gems/rcov-0.9.8/bin/rcov:511:in `load'
>>> from /usr/lib/ruby/gems/1.8/gems/rcov-0.9.8/bin/rcov:511
>>> from /usr/bin/rcov:19:in `load'
>>> from /usr/bin/rcov:19
>>> Please help me.
>> 
>> Please show me what  you typed in your config/environment.rb to 
>> configure rspec-rails.
> 
> Hi ,
> 
> I configure the rspec-rails gem in config/environment.rb:
> 
>                config.gem "rspec-rails", :version => ">= 1.3.2"

OK - so the problem now is that you've got rspec-rails 2.0.0.beta installed and 
that satisfies the ">= 1.3.2" gem requirement, but it only works with Rails 3. 
Try changing that to this:

  config.gem "rspec-rails", :version => "~> 1.3.2"

The "~>" matches any gem versions that begin with 1.3, so if you later upgrade 
to 1.3.3 it will still work, but it won't match 2.0.0.xxx.

Also, try running with the "rake spec" command before using rcov, which adds 
complexity to the mix.

> Thanks
> Amit
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/rspec-users

_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users

Reply via email to