Rails3: in production i get uninitialised constant rspec?

Testing RSpec
1

I am trying to deploy my rails3 application in a production
environment. But when i run my first rake task:

RAILS_ENV=production rake db:setup

i always get the following result:

rake aborted!
uninitialized constant RSpec

and then points to the line in the Rakefile where it says

MyApp::Application.load_tasks

I do not have any lib/tasks referring to rspec; my gemfile does not
refer to any rspec or test gem in production.
Has anybody else encountered this?

(i have upgraded to beta.22, but encountered it with beta.20 first)

2

Whoops. Found it! I have a rcov.rake inside my lib/tasks like this:

desc “Run all specs with rcov”
RSpec::Core::RakeTask.new(“test_cov”) do |t|
t.rcov = true
t.rcov_opts = %w{–rails --include views --exclude gems/,spec
/,features/,seeds/}
end

Now i am looking for a clean way to disable this task in production
environment.
Any hints?

3

On Sep 13, 3:58 am, nathanvda [email protected] wrote:

environment.

refer to any rspec or test gem in production.
Has anybody else encountered this?

(i have upgraded to beta.22, but encountered it with beta.20 first)

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

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

unless Rails.env.production?

non-production code

end

4

On Sep 13, 1:01 am, Justin Ko [email protected] wrote:

t.rcov = true

I am trying to deploy my rails3 application in a production

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

unless Rails.env.production?

non-production code

end

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

if defined?(RSpec)
desc “Run all specs with rcov”
RSpec::Core::RakeTask.new(“test_cov”) do |t|
t.rcov = true
t.rcov_opts = %w{–rails --include views --exclude gems/,spec
/,features/,seeds/}
end
end