Skip to content

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

Closed
zpao opened this issue Jul 31, 2013 · 3 comments
Closed

Use Appraisal to test multiple Rails versions #1

zpao opened this issue Jul 31, 2013 · 3 comments

Comments

@zpao
Copy link
Member

zpao commented Jul 31, 2013

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.

@jtmalinowski
Copy link
Collaborator

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.

@zpao
Copy link
Member Author

zpao commented Aug 6, 2013

Yea, that's the coverage we need. Thanks for taking a look!

@zpao zpao mentioned this issue Aug 7, 2013
@jtmalinowski
Copy link
Collaborator

PR send here #4

@zpao zpao closed this as completed in c27d9ca Aug 20, 2013
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants