This repository has been archived by the owner. It is now read-only.
Setup testing for gem using dummy application #1
Dummy application when running:
* Drop test-unit * Generate spec following instructions from: http://stackoverflow.com/questions/8507798/rails-3-1-plugin-gem-dummy-te st-app-rspec * Create a symlink from the dummy app to the plugin spec directory * Running Rspec from root will pick up specs from the dummy app as well
Running jasmine from root prevents the spec files from being compiled through the asset pipeline. The way the jasmine gem works doesn’t play well with engines, it uses a lot of non-public APIs. By proxying the rake task through to the dummy app we fool jasmine into thinking it’s testing a full rails app, and we get the test and test results we need.
* Reduce noise and simplify dummy application * Followed instructions from http://stackoverflow.com/questions/3954307/rails-3-how-do-i-avoid-databa se-altogether
The number of combinations of dependencies was so large that Bundler was taking a very long time (forever?) to resolve the dependencies. Pinning the dev dependencies doesn't affect users of the gem. Also require Rails 3.2 and above - not strictly required in this change, but all of our apps are on 3.2 and above anyway.
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments.