Menu
Right now, I'm using bundler to manage my gems. Bundler loads different gems for different environments.
I have some rake tasks that use testing gems (rspec), but these cause problems in production environments where that gem isn't loaded.
So what I'd like to be able to do is to only have the rake task (and the require 'rspec/core/rake_task' line associated with it) load in the test environment.
I can't quite figure out the best way to do this.
I currently have:
require "bundler"
require 'rspec/core/rake_task'
desc "Task for running Rspec tests"
RSpec::Rake::SpecTask.new(:spec)
904
Including => :environment will tell Rake to load full the application environment, giving the relevant task access to things like classes, helpers, etc. Without the :environment , you won't have access to any of those extras.
In any Rails application you can see which rake tasks are available - either by running rake -AT (or rake --all --tasks) to see all tasks, or rake -T (or rake --tasks ) to see all tasks with descriptions.
Rake is a popular task runner for Ruby and Rails applications. For example, Rails provides the predefined Rake tasks for creating databases, running migrations, and performing tests. You can also create custom tasks to automate specific actions - run code analysis tools, backup databases, and so on.
How about:
require "bundler"
unless Rails.env.production?
require 'rspec/core/rake_task'
desc "Task for running Rspec tests"
RSpec::Rake::SpecTask.new(:spec)
end
Not the prettiest solution, but it will work.
184
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
