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/4.0.1.gemfile.lock

226 lines
5 KiB
Text
Raw Normal View History

Upgrade pry to master version The latest commit of pry removes a lot of annoying warnings. Unfortunately a new release has not been issued yet, so just use the master branch for now.
2015-02-28 18:54:40 -05:00
GIT
remote: git://github.com/pry/pry.git
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
revision: 3c138cbf94a44f7a6696afdab1ab5149d7541974
Upgrade pry to master version The latest commit of pry removes a lot of annoying warnings. Unfortunately a new release has not been issued yet, so just use the master branch for now.
2015-02-28 18:54:40 -05:00
specs:
pry (0.10.1)
coderay (~> 1.1.0)
method_source (~> 0.8.1)
slop (~> 3.4)
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
remote: https://rubygems.org/
specs:
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
actionmailer (4.0.1)
actionpack (= 4.0.1)
mail (~> 2.5.4)
actionpack (4.0.1)
activesupport (= 4.0.1)
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
builder (~> 3.1.0)
erubis (~> 2.7.0)
rack (~> 1.5.2)
rack-test (~> 0.6.2)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
activemodel (4.0.1)
activesupport (= 4.0.1)
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
builder (~> 3.1.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
activerecord (4.0.1)
activemodel (= 4.0.1)
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
activerecord-deprecated_finders (~> 1.0.2)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
activesupport (= 4.0.1)
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
arel (~> 4.0.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
activerecord-deprecated_finders (1.0.4)
Fix regression with context-dependent validations in ActiveResource As reported in #348, model#valid? is called with one argument while ActiveResource::Validations only defines #valid? without an optional argument. The interface of ActiveResouce::Validations#valid? is the same for A'resource in Rails 3.2 and the one extracted into a gem. Rails 3.2 version: https://github.com/rails/rails/blob/3-2-stable/activeresource/lib/active_resource/validations.rb#L123 Gem version: https://github.com/rails/activeresource/blob/master/lib/active_resource/validations.rb#L160
2013-08-28 06:08:06 -04:00
activeresource (4.0.0)
activemodel (~> 4.0)
activesupport (~> 4.0)
rails-observers (~> 0.1.1)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
activesupport (4.0.1)
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
i18n (~> 0.6, >= 0.6.4)
minitest (~> 4.2)
multi_json (~> 1.3)
thread_safe (~> 0.1)
tzinfo (~> 0.3.37)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
ansi (1.5.0)
Bump Appraisal to 2.1.0 Why: * At some point a while back, Appraisal introduced a bug fix that made it possible to run `rspec` through `appraisal` and pass the `-e` option to target certain tests. This makes life much easier. * It's been a while since we've upgraded Appraisal anyway.
2015-09-25 18:15:01 -04:00
appraisal (2.1.0)
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
bundler
rake
Use the new appraisal executable in 1.0.0.beta1
2014-01-20 13:39:18 -05:00
thor (>= 0.14.0)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
arel (4.0.2)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
bcrypt (3.1.10)
bcrypt-ruby (3.1.5)
bcrypt (>= 3.1.3)
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
builder (3.1.4)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
byebug (5.0.0)
Use pry-byebug instead of pry-nav
2015-04-02 11:42:53 -04:00
columnize (= 0.9.0)
Add pry as development dependency
2014-02-09 07:22:25 -05:00
coderay (1.1.0)
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
coffee-rails (4.0.1)
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
coffee-script (2.4.1)
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
coffee-script-source
execjs
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
coffee-script-source (1.9.1.1)
Use pry-byebug instead of pry-nav
2015-04-02 11:42:53 -04:00
columnize (0.9.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
diff-lcs (1.2.5)
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
erubis (2.7.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
execjs (2.6.0)
fssm (0.2.10)
hashie (3.4.2)
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
hike (1.2.3)
Test against RSpec 3 from now on * Ruby 2.2 removed Minitest and Test::Unit from the standard library [[1]], [[2]] * rspec-rails requires Test::Unit for Rails versions prior to 4.1 (which switched to Minitest) * This doesn't work now, because we don't have Test::Unit present in the gem bundle * RSpec 3.2.0 fixes this issue [[3]] I don't really see this as a huge concern, since we were testing against RSpec 2.99 for Rails < 4, and that has most of the changes that RSpec 3 has. [1]: https://github.com/ruby/ruby/commit/f8c6a5dc02439bb99c8403602288c2937b9356cc [2]: https://github.com/ruby/ruby/commit/96f552670d045c3e76c02929753f6934da51974f [3]: https://github.com/rspec/rspec-rails/commit/999ebb7c5c178c462f944d792626d27dc48147b0#diff-08d960c572ac094640dd183fa9641393R13
2015-02-05 14:22:05 -05:00
i18n (0.7.0)
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
jbuilder (1.5.3)
activesupport (>= 3.0.0)
multi_json (>= 1.2.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
jquery-rails (3.1.4)
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
railties (>= 3.0, < 5.0)
thor (>= 0.14, < 2.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
json (1.8.3)
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
mail (2.5.4)
mime-types (~> 1.16)
treetop (~> 1.4.8)
Add pry as development dependency
2014-02-09 07:22:25 -05:00
method_source (0.8.2)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
mime-types (1.25.1)
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
minitest (4.7.5)
Add Cucumber setup for testing standalone Ruby applications
2014-09-12 18:39:00 -04:00
minitest-reporters (0.14.24)
ansi
builder
minitest (>= 2.12, < 5.0)
powerbar
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
multi_json (1.11.2)
pg (0.18.3)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
polyglot (0.3.5)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
posix-spawn (0.3.11)
powerbar (1.0.12)
ansi (~> 1.5.0)
Add Cucumber setup for testing standalone Ruby applications
2014-09-12 18:39:00 -04:00
hashie (>= 1.1.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
protected_attributes (1.1.3)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
activemodel (>= 4.0.1, < 5.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
pry-byebug (3.2.0)
byebug (~> 5.0)
Use pry-byebug instead of pry-nav
2015-04-02 11:42:53 -04:00
pry (~> 0.10)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
pygments.rb (0.6.3)
Generate docs using YARD
2014-06-20 00:44:06 -04:00
posix-spawn (~> 0.3.6)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
yajl-ruby (~> 1.2.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
rack (1.5.5)
Test against RSpec 3 from now on * Ruby 2.2 removed Minitest and Test::Unit from the standard library [[1]], [[2]] * rspec-rails requires Test::Unit for Rails versions prior to 4.1 (which switched to Minitest) * This doesn't work now, because we don't have Test::Unit present in the gem bundle * RSpec 3.2.0 fixes this issue [[3]] I don't really see this as a huge concern, since we were testing against RSpec 2.99 for Rails < 4, and that has most of the changes that RSpec 3 has. [1]: https://github.com/ruby/ruby/commit/f8c6a5dc02439bb99c8403602288c2937b9356cc [2]: https://github.com/ruby/ruby/commit/96f552670d045c3e76c02929753f6934da51974f [3]: https://github.com/rspec/rspec-rails/commit/999ebb7c5c178c462f944d792626d27dc48147b0#diff-08d960c572ac094640dd183fa9641393R13
2015-02-05 14:22:05 -05:00
rack-test (0.6.3)
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
rack (>= 1.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
rails (4.0.1)
actionmailer (= 4.0.1)
actionpack (= 4.0.1)
activerecord (= 4.0.1)
activesupport (= 4.0.1)
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
bundler (>= 1.3.0, < 2.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
railties (= 4.0.1)
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
sprockets-rails (~> 2.0.0)
Fix regression with context-dependent validations in ActiveResource As reported in #348, model#valid? is called with one argument while ActiveResource::Validations only defines #valid? without an optional argument. The interface of ActiveResouce::Validations#valid? is the same for A'resource in Rails 3.2 and the one extracted into a gem. Rails 3.2 version: https://github.com/rails/rails/blob/3-2-stable/activeresource/lib/active_resource/validations.rb#L123 Gem version: https://github.com/rails/activeresource/blob/master/lib/active_resource/validations.rb#L160
2013-08-28 06:08:06 -04:00
rails-observers (0.1.2)
activemodel (~> 4.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
railties (4.0.1)
actionpack (= 4.0.1)
activesupport (= 4.0.1)
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
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
Upgrade Rake This is necessary in order to use Zeus, since Rake is loaded before Bundler (and so if the version of Rake installed locally and the version in the Gemfile differ then Bundler will complain).
2016-01-25 00:08:55 -05:00
rake (10.5.0)
bundle update rdoc --full-index https://travis-ci.org/thoughtbot/shoulda-matchers/jobs/480947967 ``` Downloading rdoc-4.2.0 revealed dependencies not in the API or the lockfile (json (~> 1.4)). Either installing with `--full-index` or running `bundle update rdoc` should fix the problem. ```
2019-01-19 09:57:32 -05:00
rdoc (4.3.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
redcarpet (3.3.2)
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages.
2015-12-23 01:46:29 -05:00
rspec (3.4.0)
rspec-core (~> 3.4.0)
rspec-expectations (~> 3.4.0)
rspec-mocks (~> 3.4.0)
rspec-core (3.4.1)
rspec-support (~> 3.4.0)
rspec-expectations (3.4.0)
Test against RSpec 3 from now on * Ruby 2.2 removed Minitest and Test::Unit from the standard library [[1]], [[2]] * rspec-rails requires Test::Unit for Rails versions prior to 4.1 (which switched to Minitest) * This doesn't work now, because we don't have Test::Unit present in the gem bundle * RSpec 3.2.0 fixes this issue [[3]] I don't really see this as a huge concern, since we were testing against RSpec 2.99 for Rails < 4, and that has most of the changes that RSpec 3 has. [1]: https://github.com/ruby/ruby/commit/f8c6a5dc02439bb99c8403602288c2937b9356cc [2]: https://github.com/ruby/ruby/commit/96f552670d045c3e76c02929753f6934da51974f [3]: https://github.com/rspec/rspec-rails/commit/999ebb7c5c178c462f944d792626d27dc48147b0#diff-08d960c572ac094640dd183fa9641393R13
2015-02-05 14:22:05 -05:00
diff-lcs (>= 1.2.0, < 2.0)
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages.
2015-12-23 01:46:29 -05:00
rspec-support (~> 3.4.0)
rspec-mocks (3.4.0)
Test against RSpec 3 from now on * Ruby 2.2 removed Minitest and Test::Unit from the standard library [[1]], [[2]] * rspec-rails requires Test::Unit for Rails versions prior to 4.1 (which switched to Minitest) * This doesn't work now, because we don't have Test::Unit present in the gem bundle * RSpec 3.2.0 fixes this issue [[3]] I don't really see this as a huge concern, since we were testing against RSpec 2.99 for Rails < 4, and that has most of the changes that RSpec 3 has. [1]: https://github.com/ruby/ruby/commit/f8c6a5dc02439bb99c8403602288c2937b9356cc [2]: https://github.com/ruby/ruby/commit/96f552670d045c3e76c02929753f6934da51974f [3]: https://github.com/rspec/rspec-rails/commit/999ebb7c5c178c462f944d792626d27dc48147b0#diff-08d960c572ac094640dd183fa9641393R13
2015-02-05 14:22:05 -05:00
diff-lcs (>= 1.2.0, < 2.0)
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages.
2015-12-23 01:46:29 -05:00
rspec-support (~> 3.4.0)
rspec-rails (3.4.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
actionpack (>= 3.0, < 4.3)
activesupport (>= 3.0, < 4.3)
railties (>= 3.0, < 4.3)
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages.
2015-12-23 01:46:29 -05:00
rspec-core (~> 3.4.0)
rspec-expectations (~> 3.4.0)
rspec-mocks (~> 3.4.0)
rspec-support (~> 3.4.0)
rspec-support (3.4.1)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
sass (3.2.19)
sass-rails (4.0.5)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
railties (>= 4.0.0, < 5.0)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
sass (~> 3.2.2)
sprockets (~> 2.8, < 3.0)
sprockets-rails (~> 2.0)
sdoc (0.4.1)
json (~> 1.7, >= 1.7.7)
rdoc (~> 4.0)
shoulda-context (1.2.1)
Use pry-nav for more debugging awesomeness
2015-01-21 17:52:32 -05:00
slop (3.6.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
spring (1.4.0)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
spring-commands-rspec (1.0.4)
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
spring (>= 0.9.1)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
sprockets (2.12.4)
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
hike (~> 1.2)
multi_json (~> 1.0)
rack (~> 1.0)
tilt (~> 1.1, != 1.3.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
sprockets-rails (2.0.1)
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
actionpack (>= 3.0)
activesupport (>= 3.0)
sprockets (~> 2.8)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
sqlite3 (1.3.10)
Using RSpec 3 for development.
2014-06-17 00:54:02 -04:00
thor (0.19.1)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
thread_safe (0.3.5)
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
tilt (1.4.1)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
treetop (1.4.15)
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
polyglot
polyglot (>= 0.3.1)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
turbolinks (2.5.3)
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
coffee-rails
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages.
2015-12-23 01:46:29 -05:00
tzinfo (0.3.46)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
uglifier (2.7.2)
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
execjs (>= 0.3.0)
json (>= 1.8.0)
Remove Rails 3.x, Ruby 1.9.2, Ruby 1.9.3 Ruby 1.9.3 will be end-of-lifed on February 23, 2015. We might as well remove support for it now.
2014-10-22 00:35:12 -04:00
yajl-ruby (1.2.1)
yard (0.8.7.6)
Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb
2015-11-29 20:57:45 -05:00
zeus (0.15.4)
method_source (>= 0.6.7)
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
PLATFORMS
ruby
DEPENDENCIES
activerecord-jdbc-adapter
activerecord-jdbcsqlite3-adapter
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
activeresource (= 4.0.0)
Bump Appraisal to 2.1.0 Why: * At some point a while back, Appraisal introduced a bug fix that made it possible to run `rspec` through `appraisal` and pass the `-e` option to target certain tests. This makes life much easier. * It's been a while since we've upgraded Appraisal anyway.
2015-09-25 18:15:01 -04:00
appraisal (~> 2.0)
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
bcrypt-ruby (~> 3.1.2)
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
bundler (~> 1.1)
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
coffee-rails (~> 4.0.0)
Update appraisal gemfiles
2015-09-24 01:59:18 -04:00
fssm
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
jbuilder (~> 1.2)
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
jdbc-sqlite3
jquery-rails
jruby-openssl
Add Cucumber setup for testing standalone Ruby applications
2014-09-12 18:39:00 -04:00
minitest-reporters
Add support for Postgres When running tests, you can now switch between running them against a SQLite or PostgreSQL database. This is accomplished by modifying the unit and acceptance tests so that when they generate and load the test Rails application, database.yml is replaced with content that will configure the database appropriately.
2015-02-08 16:38:55 -05:00
pg
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
protected_attributes
Upgrade pry to master version The latest commit of pry removes a lot of annoying warnings. Unfortunately a new release has not been issued yet, so just use the master branch for now.
2015-02-28 18:54:40 -05:00
pry!
Use pry-byebug instead of pry-nav
2015-04-02 11:42:53 -04:00
pry-byebug
Generate docs using YARD
2014-06-20 00:44:06 -04:00
pygments.rb
Add Appraisal for Rails 4.0.1
2013-12-01 17:57:03 -05:00
rails (= 4.0.1)
Upgrade Rake This is necessary in order to use Zeus, since Rake is loaded before Bundler (and so if the version of Rake installed locally and the version in the Gemfile differ then Bundler will complain).
2016-01-25 00:08:55 -05:00
rake (>= 10.5.0, < 11)
Generate docs using YARD
2014-06-20 00:44:06 -04:00
redcarpet
Upgrade rspec
2015-10-08 01:26:48 -04:00
rspec (~> 3.2)
Add support for Ruby 2.2 Secondary author: Luciano Sousa <ls@lucianosousa.net> Also, upgrade to rspec-rails 3.2.0 explicitly. (See b7fe87ae915f6b1f99d64e847fea536ad0f78024 for an explanation of why 3.2.0 is necessary here.)
2014-12-28 12:54:33 -05:00
rspec-rails (>= 3.2.0, < 4)
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
sass-rails (~> 4.0.0)
sdoc
Add support to rails 4.1.0
2013-12-31 14:54:21 -05:00
shoulda-context (~> 1.2.0)
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
spring
spring-commands-rspec
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
sqlite3
therubyrhino
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
turbolinks
uglifier (>= 1.3.0)
Generate docs using YARD
2014-06-20 00:44:06 -04:00
yard
Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb
2015-11-29 20:57:45 -05:00
zeus
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages.
2015-12-23 01:46:29 -05:00
BUNDLED WITH
Upgrade Rake This is necessary in order to use Zeus, since Rake is loaded before Bundler (and so if the version of Rake installed locally and the version in the Gemfile differ then Bundler will complain).
2016-01-25 00:08:55 -05:00
1.11.2
Copy permalink