-
Notifications
You must be signed in to change notification settings - Fork 755
Use Appraisal to test multiple Rails versions #1
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
Comments
I'll take a look at it. We want to test just 3.1, 3.2, and 4.0 now, right? Ember-rails has this implemented so it shouldn't be hard. |
Yea, that's the coverage we need. Thanks for taking a look! |
Closed
rmosolgo
pushed a commit
that referenced
this issue
May 5, 2015
…e-copying fix(Railtie) add asset paths another way, add test for precompiling assets
pthrasher
added a commit
to CarLingo/react-rails
that referenced
this issue
Aug 20, 2015
handle independant apps, use shim first.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Appraisal looks pretty cool and gives us an easy way to provide coverage across Rails versions.
I started working on this but ran into some issues... I created
test/dummy
with Rails 4.0 and when loading it up with Rails 3.2 and Rails 3.1 it hit config loading issues. We might need multiple dummy apps to ensure everything actually works properly.The text was updated successfully, but these errors were encountered: