-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Upgrade to Rails 4.1 #21
base: master
Are you sure you want to change the base?
Conversation
- Add `rake test:environments` which iterates over `test/environments` and runs each file in a separate ruby process (to isolate requires) - Check presence of multiple files (.envrc, .env.example, bin/setup, etc) - Check AR validation errors are logged - Ensure presence of gems, bins and assets - Ensure SSL required in production
Rails.application.load_tasks | ||
|
||
Rake::Task['default'].clear | ||
task default: 'test:all' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should be able to just run rake
now. Or better yet autotest
.
@@ -0,0 +1,8 @@ | |||
namespace :test do | |||
desc "Run environment tests for each environment" | |||
task environments: :environment do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fancy new tests to test this rails-template. This does not get called with rake test:all
(maybe it should?). Call rake test:environments
separately to ensure all is well.
I'm creating a PR to track my progress.
Here's what's left:
DATABASE_URL
in.env
curl -L http://git.io/KebUPw|patch -p1