kotovalexarian-likes-github/thoughtbot--shoulda-matchers
1
0
Fork 0
mirror of https://github.com/thoughtbot/shoulda-matchers.git synced 2022-11-09 12:01:38 -05:00
Code Releases Activity
thoughtbot--shoulda-matchers/gemfiles/3.2.gemfile

36 lines
877 B
Text
Raw Normal View History

Test against Rails 3.2.
2012-03-09 10:53:23 -05:00
# This file was generated by Appraisal
Loosen Bourne dependency to ~> 1.3 > Use a pessimistic version in the Gemfile for gems that follow semantic > versioning, such as rspec, factory_girl, and capybara. https://github.com/thoughtbot/guides/tree/master/best-practices * Upgrade dependencies so specs run on new Bourne. * Use semantic versions in step_definitions gems. * Rely on ActiveSupport::Dependencies.clear for reloading constants. http://rkh.im/code-reloading
2013-03-18 03:19:06 -04:00
source "https://rubygems.org"
Test against Rails 3.2.
2012-03-09 10:53:23 -05:00
Upgrade to appraisal 1.0.2
2014-10-22 02:16:26 -04:00
gem "appraisal", "~> 1.0"
Move dev dependencies to Gemfile Currently some dev dependencies are in the Gemfile, and some are in the gemspec. The dependencies in the Gemfile are there because they are using Bundler-specific options, so there is a legitimate reason for them to be there, however, it's confusing to have gems in two places. So the common denominator is to have them in the Gemfile.
2014-01-22 17:21:52 -05:00
gem "aruba"
gem "bourne", "~> 1.3"
gem "bundler", "~> 1.1"
gem "pry"
Upgrade to appraisal 1.0.2
2014-10-22 02:16:26 -04:00
gem "rails", "~> 3.2.13"
Move dev dependencies to Gemfile Currently some dev dependencies are in the Gemfile, and some are in the gemspec. The dependencies in the Gemfile are there because they are using Bundler-specific options, so there is a legitimate reason for them to be there, however, it's confusing to have gems in two places. So the common denominator is to have them in the Gemfile.
2014-01-22 17:21:52 -05:00
gem "rake", ">= 0.9.2"
Upgrade to appraisal 1.0.2
2014-10-22 02:16:26 -04:00
gem "rspec-rails", "2.99.0"
Generate docs using YARD
2014-06-20 00:44:06 -04:00
gem "yard"
gem "redcarpet"
gem "pygments.rb"
gem "watchr"
Add support to rails 4.1.0
2013-12-31 14:54:21 -05:00
gem "shoulda-context", "~> 1.2.0"
Upgrade to appraisal 1.0.2
2014-10-22 02:16:26 -04:00
gem "sqlite3", :platform => :ruby
gem "activerecord-jdbc-adapter", :platform => :jruby
gem "activerecord-jdbcsqlite3-adapter", :platform => :jruby
gem "jdbc-sqlite3", :platform => :jruby
gem "jruby-openssl", :platform => :jruby
gem "therubyrhino", :platform => :jruby
Add missing test dependences to Appraisals Since as of commit 2748b750873faf587c78d7a71f6c725b0fd4252a, we no longer install dependencies inside of the Rails app that is generated and used to run all of the tests, we have to require all of the dependencies that the app would install inside of the appropriate Appraisals. This was mostly straightforward except for some workarounds with the turn gem: * Rails 3.1 requires two versions of turn depending on which Ruby version you're using. On 1.9.2, it uses turn 0.9.2; after 1.9.2, it uses ~> 0.9.3. To accommodate this we have to have two versions of the Rails 3.1 appraisal which declare the different turn versions. * Rails 3.1 also loads the turn gem even if, in the Gemfile for the app, turn is declared with `require: false`. This causes a problem while running our tests because turn actually requires minitest/autorun, which adds a hook so when Ruby exits, Minitest tests are run. Because we're already using RSpec, Minitest will try to re-run the `rspec` command we ran within a Minitest environment. This will fail since we are using RSpec-specific command line options to run the tests. Unfortunately there's no way to shut off minitest/autorun after it's been required, so we have to monkey-patch Minitest's #run method so it's a no-op.
2014-05-16 11:57:19 -04:00
gem "strong_parameters"
Upgrade to appraisal 1.0.2
2014-10-22 02:16:26 -04:00
gem "minitest", "~> 4.0"
gem "minitest-reporters"
Add have_secure_password matcher
2013-08-18 13:17:19 -04:00
gem "bcrypt-ruby", "~> 3.0.0"
Test against Rails 3.2.
2012-03-09 10:53:23 -05:00
gem "jquery-rails"
Add missing test dependences to Appraisals Since as of commit 2748b750873faf587c78d7a71f6c725b0fd4252a, we no longer install dependencies inside of the Rails app that is generated and used to run all of the tests, we have to require all of the dependencies that the app would install inside of the appropriate Appraisals. This was mostly straightforward except for some workarounds with the turn gem: * Rails 3.1 requires two versions of turn depending on which Ruby version you're using. On 1.9.2, it uses turn 0.9.2; after 1.9.2, it uses ~> 0.9.3. To accommodate this we have to have two versions of the Rails 3.1 appraisal which declare the different turn versions. * Rails 3.1 also loads the turn gem even if, in the Gemfile for the app, turn is declared with `require: false`. This causes a problem while running our tests because turn actually requires minitest/autorun, which adds a hook so when Ruby exits, Minitest tests are run. Because we're already using RSpec, Minitest will try to re-run the `rspec` command we ran within a Minitest environment. This will fail since we are using RSpec-specific command line options to run the tests. Unfortunately there's no way to shut off minitest/autorun after it's been required, so we have to monkey-patch Minitest's #run method so it's a no-op.
2014-05-16 11:57:19 -04:00
gem "sass-rails", "~> 3.2.3"
gem "coffee-rails", "~> 3.2.1"
gem "uglifier", ">= 1.0.3"
Use same assertion class as Rails, if loaded Given this scenario: * Using Rails 4.1 * Gemfile has `gem 'shoulda-matchers', require: false` * spec_helper has `require 'shoulda/matchers'` following `require 'rspec/rails'` * Using Spring to run tests matchers that delegate to assertions in Rails (e.g. `render_template` and `route`) will fail in the wrong way if used. They fail because in order to use these assertions, we expect that the assertions will raise a specific exception, an exception that corresponds to whichever test framework that Rails is using. For Rails versions that used Test::Unit, this is Test::Unit::AssertionFailedError. For current Rails versions, which now use Minitest, this exception is Minitest::Assertion. The problem is that instead of asking Rails which exception class it's using, we are trying to detect this exception class ourselves (for cases in which Rails is not being used). This leads to the wrong class being detected: when using a Rails version that uses Minitest, we choose Test::Unit::AssertionFailedError as the class. This happens using the exact scenario above because even though shoulda-matchers is loaded after rspec-rails, rspec-rails itself defines Test::Unit::AssertionFailedError. Also add Cucumber tests that confirms this exact scenario works.
2014-06-21 23:24:22 -04:00
gem "spring"
gem "spring-commands-rspec"
Test against Rails 3.2.
2012-03-09 10:53:23 -05:00
Upgrade to appraisal 1.0.2
2014-10-22 02:16:26 -04:00
gemspec :path => "../"
Copy permalink