To get the test suite to run in under 2.2, I: * Upgraded Cucumber to a version that supports Ruby 2.2 * Added 2.2.0 to our Travis Matrix (Sorry, Travis) * Excluded Rails 3.2 under Ruby 2.2 from appraisals as it is not supported by rails (yet). See: rails/rails#18306 Once that was done, it was discovered that Rails 4.0.x requires the `test-unit` gem under Ruby 2.2. Adding that gem allows the test suite to run there. With that in place, I found that the `deny_access` matcher was not negating as expected. This is because the test-unit gem raises a different error when an assertion failed. I have to catch this error in addition to the Minitest::Assertion error we were already catching.
The Travis container infrastructure supports bundler caching for open source builds. For projects with a Gemfile.lock, this can significantly speed up builds. In our case it may not result in as big of a speedup due to the need to install the gems for our various appraisals.
This isn't library code, it's test code. It doesn't belong in `lib`. Common convention in engines is to have the dummy app in `spec/dummy`. * Update namespace so it doesn't look like part of Clearance. * Update reference from `Clearance::Testing::Application` to `Dummy::Application`. * Move dummy rake tasks into the `dummy` rake namespace. * Update bin/setup to use the new namespace. * Update bin/setup to no longer clean old appraisals out. * Update style in Rakefile and Dummy app
Travis frequently has timeout problems when contacting rubygems. Travis supplies the `travis_retry` command to help combat this. This will retry the install up to 3 times. This will not help when appraisal tries to install its missing dependencies. Changes for that are probably best left to appraisal.
* Add Ruby 2.1 to travis configuration * Update Rails 3.2 and 4.0 appraisals to latest versions * Add I18n.enforce_available_locales setting to test app to avoid deprecation warning. * Add Rails 4.1.0.beta1 to appraisals * Test unit integration feature updated to account for differing test output under rails 4.1 * Update gems
Also need to update rubygems along with the certs to keep from getting cert errors when bundling. See: http://stackoverflow.com/questions/19150017/ssl-error-when-installing-rubygems-unable-to-pull-data-from-https-rubygems-o
Force `bundle install` in install step Travis will now runs `bundle install --deployment` if it detects that the project has `Gemfile.lock`. However, there's a problem in Bundler deployment install that cause it not installing `bundler` gem into `vendor/bundle` directory, which causes `require 'bundler'` to fail.
There were issues with activesupport 4 and Ruby 1.9.2: https://travis-ci.org/thoughtbot/clearance/jobs/9306920
There was an issue where Travis build was erring because the bundler version was 1.2.3, and we explicitly upgrade rubygems via travis.yml. Thus, the result was that rubygems 2.0 is no longer compatible with older bundler versions. Thus let's always grab the latest version of bundler for Travis builds.
…ppraisal run to happen for each