CARVIEW |
Every repository with this icon (

Every repository with this icon (

No gems have been built for this project yet.
Description: | RSpec's official Ruby on Rails plugin |
Clone URL: |
git://github.com/dchelimsky/rspec-rails.git
Give this clone URL to anyone.
git clone git://github.com/dchelimsky/rspec-rails.git
|
Comments for dchelimsky's rspec-rails


Sorry for the links in my previous comment, the formatting used the closing parentheses for the url. The links are:

I think it will be easier to use a more standard solution here using RUBYOPT env var and not this odd named var. Something like if !ENV[‘RUBYOPT’].include?(“rubygems”).

Shame to have all this duplication, but these scripts are figuring out where to load from. Catch 22.

Why does rspec.rake now delete other dependencies on
:default?
This stops keeps the default task from running:features
too. Obviously I can delete it in my own rspec.rake, but I want to make sure there isn’t an important reason for it.

David, I’m getting dependency errors now that the ‘dchelimsky_’ prefix is gone. This has happened in the past – is there a way round that works? I have installed with the —force option, but the dependency is now raised when I run my specs…

By the way, I’m thinking of this commit:

Doesn’t this change make the warning in spec_server about setting config.cache_classes to false unnecessary?

I believe this needs to be Rack::Utils.parse_nested_query(query) instead

Hi, commit comment should be: “warn that spec_server won’t reload classes if config.cache_classes=TRUE”, right?

I think this has been fixed in now.

I pasted this latest version of the rake task into my rails project as I’ve found this problem with rspec-rails not being installed when running rake but it still fails due to environment trying to load in the rescue block and failing on the config.gem ‘rspec-rails’ require. As I’m trying to do rake gems:install this still seems to be a bit of a catch-22. I just replaced the rescue block with puts ‘RSpec not installed. Skipping…’ and this fixed it. Obviously things will go nasty if you try to run one of the RSpec tasks.

Writing a test for this was pretty painful since it would involve defining methods and loading stuff and then undefining and reloading and blah blah…didn’t think it was worth it. If any weird errors related to rendering crop up, I’ll take another look at this

I am using restful-authentication, and now I am getting this failing test:

attribute.default_value should really be attribute.default.inspect