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.0.gemfile

28 lines
681 B
Text
Raw Normal View History

Add Appraisals to the project to handle testing against multiple Rails version Note that we also bump RSpec to 2.6.1.beta1 because the incompatibility with Rails 3.1.0.rc1
2011-05-25 14:38:07 -04: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 00:19:06 -07:00
source "https://rubygems.org"
Add Appraisals to the project to handle testing against multiple Rails version Note that we also bump RSpec to 2.6.1.beta1 because the incompatibility with Rails 3.1.0.rc1
2011-05-25 14:38:07 -04:00
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 15:21:52 -07:00
gem "appraisal", "~> 1.0.0.beta2"
gem "aruba"
gem "bourne", "~> 1.3"
gem "bundler", "~> 1.1"
gem "cucumber", "~> 1.1"
gem "pry"
gem "rake", ">= 0.9.2"
gem "rspec-rails", ">= 2.13.1", "< 3"
Generate docs using YARD
2014-06-19 22:44:06 -06:00
gem "yard"
gem "redcarpet"
gem "pygments.rb"
gem "watchr"
Add support to rails 4.1.0
2013-12-31 17:54:21 -02:00
gem "shoulda-context", "~> 1.2.0"
Update set_the_flash_matcher to also duplicate the used set to fix a bug in Rubinius Tests now also passed on Rubinius 2.0
2011-09-19 00:27:47 +07:00
gem "sqlite3", :platform=>:ruby
gem "activerecord-jdbc-adapter", :platform=>:jruby
render_template compatible with assert_template, closes #21
2011-10-15 14:33:51 +03:00
gem "activerecord-jdbcsqlite3-adapter", :platform=>:jruby
Update set_the_flash_matcher to also duplicate the used set to fix a bug in Rubinius Tests now also passed on Rubinius 2.0
2011-09-19 00:27:47 +07:00
gem "jdbc-sqlite3", :platform=>:jruby
render_template compatible with assert_template, closes #21
2011-10-15 14:33:51 +03:00
gem "jruby-openssl", :platform=>:jruby
Add therubyrhino for jruby on 3.1.4.
2012-04-13 10:12:15 -04:00
gem "therubyrhino", :platform=>:jruby
Add Rails 4 Appraisal Rails 4 includes strong parameters and removed attr_accessible (protected attributes). I removed the strong_parameters development dependency and added it to all non-4.0 appraisals. I also added the 'protected_attributes' gem to the 4.0 appraisal because the test suite examples make heavy use of attr_accessible.
2013-05-10 13:13:48 -04:00
gem "strong_parameters"
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 09:57:19 -06:00
gem "rails", "~> 3.0.17"
Add Appraisals to the project to handle testing against multiple Rails version Note that we also bump RSpec to 2.6.1.beta1 because the incompatibility with Rails 3.1.0.rc1
2011-05-25 14:38:07 -04:00
Use the new appraisal executable in 1.0.0.beta1
2014-01-20 11:39:18 -07:00
gemspec :path=>".././"
Copy permalink