mcmire-shoulda-matchers 2.5.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: c096e55f73b803885444d4c6403f05d415c2b46b
+  data.tar.gz: 98132edf5cea73a593f1ce2ffbd61a0412e7443a
+SHA512:
+  metadata.gz: 46e4382716b1e65c0c26231207e1663324164283f16425e9888b6cab729121b7b65f29703620b95bd7eee66d44474ff1eda17b0cdbb5761cf0d0c33006aa2def
+  data.tar.gz: a8c5297f2e1e6d10cbd4526db01fa884855a608d3cc30201b3e5cd9e547bb14d3f419278a92588cd6326aa45c24c1b53459d4059e33ed4c616d1ba3803bc55cb

data/.gitignore

@@ -0,0 +1,12 @@
+*.rbc
+*.swo
+*.swp
+.bundle
+.gh-pages
+.svn/
+.yardoc
+coverage
+pkg
+tags
+test/*/log/*.log
+tmp

data/.travis.yml

@@ -0,0 +1,32 @@
+script: "bundle exec rake spec cucumber"
+
+install: "travis_retry bundle install"
+
+rvm:
+  - 1.9.2
+  - 1.9.3
+
+gemfile:
+  - gemfiles/3.0.gemfile
+  - gemfiles/3.1.gemfile
+  - gemfiles/3.2.gemfile
+
+matrix:
+  allow_failures:
+    - rvm: rbx-19mode
+    - rvm: jruby-19mode
+  include:
+    - rvm: 1.9.3
+      gemfile: gemfiles/4.0.0.gemfile
+    - rvm: 1.9.3
+      gemfile: gemfiles/4.0.1.gemfile
+    - rvm: 2.0.0
+      gemfile: gemfiles/3.2.gemfile
+    - rvm: 2.0.0
+      gemfile: gemfiles/4.0.0.gemfile
+    - rvm: 2.0.0
+      gemfile: gemfiles/4.0.1.gemfile
+    - rvm: rbx-19mode
+      gemfile: gemfiles/3.2.gemfile
+    - rvm: jruby-19mode
+      gemfile: gemfiles/3.2.gemfile

data/.yardopts

@@ -0,0 +1,7 @@
+--no-private
+--protected
+--files README.md lib/**/*.rb
+--markup markdown
+--hide-tag return
+--hide-tag param
+-e ./doc_config/yard/setup.rb

data/Appraisals

@@ -0,0 +1,45 @@
+rails_4_0 = proc do
+  gem 'jquery-rails'
+  gem 'activeresource', '4.0.0'
+  # Test suite makes heavy use of attr_accessible
+  gem 'protected_attributes'
+end
+
+#---
+
+if RUBY_VERSION < '2.0'
+  appraise '3.0' do
+    gem 'rails', '~> 3.0.17'
+    gem 'strong_parameters'
+  end
+
+  appraise '3.1' do
+    gem 'rails', '~> 3.1.8'
+    gem 'bcrypt-ruby', '~> 3.0.0'
+    gem 'jquery-rails'
+    gem 'sass-rails'
+    gem 'strong_parameters'
+  end
+end
+
+appraise '3.2' do
+  gem 'rails', '~> 3.2.13'
+  gem 'bcrypt-ruby', '~> 3.0.0'
+  gem 'jquery-rails'
+  gem 'sass-rails'
+  gem 'strong_parameters'
+end
+
+appraise '4.0.0' do
+  instance_eval(&rails_4_0)
+  gem 'rails', '4.0.0'
+  gem 'sass-rails', '4.0.0'
+  gem 'bcrypt-ruby', '~> 3.0.0'
+end
+
+appraise '4.0.1' do
+  instance_eval(&rails_4_0)
+  gem 'rails', '4.0.1'
+  gem 'sass-rails', '4.0.1'
+  gem 'bcrypt-ruby', '~> 3.1.2'
+end

data/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+We love pull requests. Here's a quick guide:
+
+1. Fork the repo.
+
+2. Run the tests. We only take pull requests with passing tests, and it's great
+to know that you have a clean slate: `bundle && bundle exec rake`
+
+3. Add a test for your change. Only refactoring and documentation changes
+require no new tests. If you are adding functionality or fixing a bug, we need
+a test!
+
+4. Make the test pass.
+
+5. Update NEWS.md with a brief description of your changes under the HEAD
+   heading.
+
+6. Push to your fork and submit a pull request.
+
+
+At this point you're waiting on us. We like to at least comment on, if not
+accept, pull requests within three business days (and, typically, one business
+day). We may suggest some changes or improvements or alternatives.
+
+Some things that will increase the chance that your pull request is accepted,
+taken straight from the Ruby on Rails guide:
+
+* Use Rails idioms and helpers
+* Include tests that fail without your code, and pass with it
+* Update the documentation, the surrounding one, examples elsewhere, guides,
+  whatever is affected by your contribution
+
+Syntax:
+
+* Two spaces, no tabs.
+* No trailing whitespace. Blank lines should not have any space.
+* Prefer &&/|| over and/or.
+* MyClass.my_method(my_arg) not my_method( my_arg ) or my_method my_arg.
+* a = b and not a=b.
+* Follow the conventions you see used in the source already.
+
+And in case we didn't emphasize it enough: we love tests!

data/Gemfile

@@ -0,0 +1,31 @@
+source 'https://rubygems.org'
+
+gemspec
+
+gem 'appraisal', '~> 1.0.0.beta2'
+gem 'aruba'
+gem 'bourne', '~> 1.3'
+gem 'bundler', '~> 1.1'
+gem 'cucumber', '~> 1.1'
+gem 'pry'
+gem 'rails', '~> 3.0'
+gem 'rake', '>= 0.9.2'
+gem 'rspec-rails', '>= 2.13.1', '< 3'
+
+# YARD
+gem 'yard'
+gem 'redcarpet'
+gem 'pygments.rb'
+gem 'watchr'
+
+# For test Rails application
+gem 'shoulda-context', '~> 1.1.2'
+gem 'sqlite3', :platform => :ruby
+
+# Can't wrap in platform :jruby do...end block because appraisal doesn't
+# support it
+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

data/Gemfile.lock

@@ -0,0 +1,166 @@
+PATH
+  remote: .
+  specs:
+    mcmire-shoulda-matchers (2.5.0)
+      activesupport (>= 3.0.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actionmailer (3.2.16)
+      actionpack (= 3.2.16)
+      mail (~> 2.5.4)
+    actionpack (3.2.16)
+      activemodel (= 3.2.16)
+      activesupport (= 3.2.16)
+      builder (~> 3.0.0)
+      erubis (~> 2.7.0)
+      journey (~> 1.0.4)
+      rack (~> 1.4.5)
+      rack-cache (~> 1.2)
+      rack-test (~> 0.6.1)
+      sprockets (~> 2.2.1)
+    activemodel (3.2.16)
+      activesupport (= 3.2.16)
+      builder (~> 3.0.0)
+    activerecord (3.2.16)
+      activemodel (= 3.2.16)
+      activesupport (= 3.2.16)
+      arel (~> 3.0.2)
+      tzinfo (~> 0.3.29)
+    activeresource (3.2.16)
+      activemodel (= 3.2.16)
+      activesupport (= 3.2.16)
+    activesupport (3.2.16)
+      i18n (~> 0.6, >= 0.6.4)
+      multi_json (~> 1.0)
+    appraisal (1.0.0.beta2)
+      bundler
+      rake
+      thor (>= 0.14.0)
+    arel (3.0.3)
+    aruba (0.5.3)
+      childprocess (~> 0.3.6)
+      cucumber (>= 1.1.1)
+      rspec-expectations (>= 2.7.0)
+    bourne (1.5.0)
+      mocha (>= 0.13.2, < 0.15)
+    builder (3.0.4)
+    childprocess (0.3.9)
+      ffi (~> 1.0, >= 1.0.11)
+    coderay (1.1.0)
+    cucumber (1.3.10)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.12)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.0.2)
+    diff-lcs (1.2.5)
+    erubis (2.7.0)
+    ffi (1.9.3)
+    gherkin (2.12.2)
+      multi_json (~> 1.3)
+    hike (1.2.3)
+    i18n (0.6.9)
+    journey (1.0.4)
+    json (1.8.1)
+    mail (2.5.4)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
+    metaclass (0.0.1)
+    method_source (0.8.2)
+    mime-types (1.25.1)
+    mocha (0.14.0)
+      metaclass (~> 0.0.1)
+    multi_json (1.8.4)
+    multi_test (0.0.3)
+    polyglot (0.3.3)
+    posix-spawn (0.3.8)
+    pry (0.9.12.6)
+      coderay (~> 1.0)
+      method_source (~> 0.8)
+      slop (~> 3.4)
+    pygments.rb (0.3.7)
+      posix-spawn (~> 0.3.6)
+      yajl-ruby (~> 1.1.0)
+    rack (1.4.5)
+    rack-cache (1.2)
+      rack (>= 0.4)
+    rack-ssl (1.3.3)
+      rack
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    rails (3.2.16)
+      actionmailer (= 3.2.16)
+      actionpack (= 3.2.16)
+      activerecord (= 3.2.16)
+      activeresource (= 3.2.16)
+      activesupport (= 3.2.16)
+      bundler (~> 1.0)
+      railties (= 3.2.16)
+    railties (3.2.16)
+      actionpack (= 3.2.16)
+      activesupport (= 3.2.16)
+      rack-ssl (~> 1.3.2)
+      rake (>= 0.8.7)
+      rdoc (~> 3.4)
+      thor (>= 0.14.6, < 2.0)
+    rake (10.1.1)
+    rdoc (3.12.2)
+      json (~> 1.4)
+    redcarpet (3.0.0)
+    rspec-core (2.14.7)
+    rspec-expectations (2.14.4)
+      diff-lcs (>= 1.1.3, < 2.0)
+    rspec-mocks (2.14.4)
+    rspec-rails (2.14.1)
+      actionpack (>= 3.0)
+      activemodel (>= 3.0)
+      activesupport (>= 3.0)
+      railties (>= 3.0)
+      rspec-core (~> 2.14.0)
+      rspec-expectations (~> 2.14.0)
+      rspec-mocks (~> 2.14.0)
+    shoulda-context (1.1.6)
+    slop (3.4.7)
+    sprockets (2.2.2)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    sqlite3 (1.3.8)
+    thor (0.18.1)
+    tilt (1.4.1)
+    treetop (1.4.15)
+      polyglot
+      polyglot (>= 0.3.1)
+    tzinfo (0.3.38)
+    watchr (0.7)
+    yajl-ruby (1.1.0)
+    yard (0.8.7.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activerecord-jdbc-adapter
+  activerecord-jdbcsqlite3-adapter
+  appraisal (~> 1.0.0.beta2)
+  aruba
+  bourne (~> 1.3)
+  bundler (~> 1.1)
+  cucumber (~> 1.1)
+  jdbc-sqlite3
+  jruby-openssl
+  mcmire-shoulda-matchers!
+  pry
+  pygments.rb
+  rails (~> 3.0)
+  rake (>= 0.9.2)
+  redcarpet
+  rspec-rails (>= 2.13.1, < 3)
+  shoulda-context (~> 1.1.2)
+  sqlite3
+  therubyrhino
+  watchr
+  yard

data/MIT-LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2006-2014, Tammer Saleh, thoughtbot, inc.
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.

data/NEWS.md

@@ -0,0 +1,299 @@
+# HEAD
+
+* Association matchers now test that the model being referred to (either
+  implicitly or explicitly, using `:class_name`) actually exists.
+
+* Add ability to test `:autosave` option on associations.
+
+* Fix `validate_uniqueness_of(...).allow_nil` so that it can be used against an
+  non-password attribute which is in a model that `has_secure_password`. Doing
+  so previously would result in a "Password digest missing on new record" error.
+
+* Fix description for `validate_numericality_of` so that if the matcher fails,
+  the error message reported does not say the matcher accepts integer values if
+  you didn't specify that.
+
+* Fix `ensure_inclusion_of` so that you can use it against a boolean column
+  (and pass boolean values to `in_array`). There are two caveats:
+
+  * You should not test that your attribute allows both true and false
+    (`.in_array([true, false]`); there's no way to test that it doesn't accept
+    anything other than that.
+  * You cannot test that your attribute allows nil (`.in_array([nil])`) if
+    the column does not allow null values.
+
+* Change `validate_uniqueness_of(...)` so that it provides default values for
+  non-nullable attributes.
+
+* Running `rake` now installs Appraisals before running the test suite.
+
+* Additionally, we now manage Appraisals using the `appraisal` executable that
+  is coming in Appraisal 1.0.0 (we're using the beta for now).
+
+* Add `allow_nil` option to `validate_numericality_of` so that you can validate
+  that numeric values are validated only if a value is supplied.
+
+* Fix `validate_numericality_of` so that test fails when the value with
+  `greater_than`, `greater_than_or_equal_to`, `less_than`, `less_than_or_equal_
+  to` or `equal_to` is not appropriate.
+
+# v 2.5.0
+
+* Fix Rails/Test::Unit integration to ensure that the test case classes we are
+  re-opening actually exist.
+
+* Fix `ensure_length_of` so that it uses the right message to validate when
+  `is_equal_to` is specified in conjunction with a custom message.
+
+* The `route` matcher now accepts specifying a controller/action pair as a
+  string instead of only a hash (e.g. `route(...).to('posts#index')` instead of
+  `route(...).to(controller: 'posts', action: 'index')`).
+
+* The `ensure_inclusion_of` matcher now works with a decimal column.
+
+* Under Rails 3, if you had an association matcher chained with the
+  the `order` submatcher -- e.g. `should have_many(:foos).order(:bar)` -- and
+  your association had an `:include` on it, using the matcher would raise an
+  error. This has been fixed.
+
+* Fix `validate_uniqueness_of` so it doesn't fail if the attribute under
+  test has a limit of fewer than 16 characters.
+
+* You can now test that your `has_many :through` or `has_one :through`
+  associations are defined with a `:source` option.
+
+* Add new matcher `validates_absence_of`.
+
+* Update matchers so that they use `failure_message` and
+  `failure_message_when_negated` to define error messages. These are new methods
+  in the upcoming RSpec 3 release which replace `failure_message_for_should` and
+  `failure_message_for_should_not`. We've kept backward compatibility so all of
+  your existing tests should still work -- this is just to make sure when RSpec
+  3 is released you don't get a bunch of warnings.
+
+# v 2.4.0
+
+* Fix a bug with the `validate_numericality_of` matcher that would not allow the
+  `with_message` option on certain submatchers.
+
+* Fix a regression with context-dependent validations in ActiveResource
+
+* shoulda-matchers is now fully compatible with Rails 4.
+
+* When not using RSpec, shoulda-matchers is now auto-included into
+  ActiveSupport::TestCase instead of Test::Unit::TestCase (in Rails 4
+  the former no longer inherits from the latter).
+
+# v 2.3.0
+
+* Fix a bug in `ensure_inclusion_of` that would cause issues with using
+  `in_array` with an integer value.
+
+* Add support for PostgreSQL UUID columns to `validates_uniqueness_of` (#334).
+
+* Fix `validates_numericality_of` so that `is_equal_to` submatcher works
+  correctly (#326).
+
+* Fix context support for validation matchers and disallowed values (#313).
+
+* Add a `counter_cache` submatcher for `belongs_to` associations (#311).
+
+* Add a `rescue_from` matcher for Rails controllers which checks that the
+  correct ActiveSupport call has been made and that the handlers exist without
+  actually throwing an exception (#287).
+
+* Changed the scope of AssociationMatcher methods from protected to private.
+
+* Extracted `#order`, `#through`, and `#dependent` from AssociationMatcher as
+  their own submatchers.
+
+# v 2.2.0
+
+* Fix `have_and_belong_to_many` matcher issue for Rails 4.
+
+* Fix `validate_uniqueness_of.scoped_to` issue when the scoped field is already
+  taken (#207).
+
+* Add comparison submatchers to `validate_numericality_of` to correspond to the
+  comparison options you can give to `validates_numericality_of` (#244).
+
+# v 2.1.0
+
+* Add missing `failure_message_for_should_not` implementations to
+`validate_numericality_of` and its submatchers
+
+* Support validation contexts for testing validations `on: :create` and when
+  using custom contexts like `model.valid?(:my_context)`.
+
+* Fix a bug in validations with autosaved models.
+
+* Fix maximum value detection for the `ensure_inclusion_of` and
+`ensure_exclusion_of` matchers.
+
+* Add `:odd` and `:even` options to the `validate_numericality_of` matcher.
+
+* Add `:touch` option to AssociationMatcher.
+
+* Ruby 2.0.0 is now officially supported.
+
+* Fix the issue where using `%{attribute}` or `%{model}` in I18n translations
+raised exceptions.
+
+* Support datetime columns in `validate_uniqueness_of.scoped_to`.
+
+* Add `allow_nil` option to the `validate_uniqueness_of` matcher.
+
+# v 2.0.0
+* Remove the following matchers:
+  * `assign_to`
+  * `respond_with_content_type`
+  * `query_the_database`
+  * `validate_format_of`
+  * `have_sent_email`
+  * `permit` (strong parameters matcher)
+  * `delegate_method`
+
+* For more information about 2.0 changes, see:
+http://robots.thoughtbot.com/post/47031676783/shoulda-matchers-2-0.
+
+# v 1.5.6
+* Revert previous change in AllowValueMatcher that added a check for a
+properly-set attribute.
+
+# v 1.5.5
+* AllowValueMatcher checks that the right value is used for attempts at
+setting the attribute with it.
+  * Please note that previously-passing tests might now fail. It is likely that
+  it's not a bug, but please make sure that the code you're testing is written
+  properly before submitting an issue.
+
+* Use DisallowValueMatcher for `disallows_value_of` method.
+
+* Assert `class_name` value on real class name for AssociationMatcher.
+
+* Correct the variable used for `validate_confirmation_of` matcher description.
+
+# v 1.5.4
+* Properly-released version of 1.5.3.
+
+# v 1.5.3 - yanked due to mis-release
+* Alleviate the need to add `rspec` gem to your app.
+
+# v 1.5.1
+* Bump version dependency of Bourne to allow for Mocha upgrade.
+
+* Should fix incompatibility with MiniTest.
+
+# v 1.5.0
+* Deprecate the following matchers:
+  * `assign_to`
+  * `respond_with_content_type`
+  * `query_the_database`
+  * `validate_format_of`
+  * `have_sent_email`
+  * `permit` (strong parameters matcher)
+  * `delegate_method`
+
+* Use RSpec's native `configure.include` syntax for including matchers into
+  RSpec (#204).
+
+* Do not force MiniTest loading when test-unit is available (this was fixed
+  before 1.3.0 then reverted in 1.3.0).
+
+# v1.4.2
+* Add a new `delegate_method` matcher.
+
+# v1.4.1
+* Fix an issue when used with Test::Unit on the allow value matcher.
+
+* Fix an issue with using `ensure_inclusion_of(:attr)` given an array of true or false values.
+
+# v1.4.0
+
+* Add `strict` option to validation matchers.
+
+* Verify that arguments to `set_the_flash` matcher are valid.
+
+* Fix issue in ValidateUniquenessMatcher that could cause an error on postgres.
+
+* You can now pass an array to `ensure_exclusion_of` using `in_array`.
+
+* Allow testing of `:foreign_key` option for `has_one` relationships using the association matcher.
+
+* Fix bug where `ensure_length_of` would pass if the given string was too long.
+
+* `allow_blank` will now allow values such as: ' ', '\n', and '\r'.
+
+* Test outside values for `ensure_inclusion_of` when given an array.
+
+* Fix the output of the `set_the_flash` matcher.
+
+# v1.3.0
+
+* `validate_format_of` will accept `allow_blank(bool)` and `allow_nil(bool)`.
+
+* Prefer Test::Unit to MiniTest when loading integrations so that RubyMine is
+  happy (#88).
+
+* `validates_uniqueness_of` will now create a record if one does not exist.
+  Previously, users were required to create a record in the database before
+  using this matcher.
+
+* Fix an edge case when where the matchers weren't loaded into Test::Unit when
+  mixing RSpec and Test::Unit tests and also loading both the 'rspec-rails' gem
+  and 'shoulda-matchers' gem from the same Gemfile group, namely [:test,
+  :development].
+
+* `controller.should_not render_partial` now correctly matches `render partial: "partial"`.
+
+# v1.2.0
+
+* `ensure_inclusion_of` now has an `in_array` parameter:
+  `ensure_inclusion_of(:attr).in_array(['foo', 'bar'])`. It cannot be used with
+  the `.in_range` option. (vpereira)
+
+* `ensure_in_inclusion_of` with `in_array` will accept `allow_blank(bool)` and `allow_nil(false)`
+
+* Test against Rails 3.2.
+
+* Fix `ensure_length_of` to use all possible I18n error messages.
+
+* `have_db_index.unique(nil)` used to function exactly the same as
+  `have_db_index` with no unique option. It now functions the same as
+  `have_db_index.unique(false)`.
+
+* In 1.1.0, `have_sent_email` checked all emails to ensure they matched. It now
+  checks that only one email matches, which restores 1.0.0 behavior.
+
+# v1.1.0
+
+* Add `only_integer` option to `validate_numericality_of`:
+  `should validate_numericality_of(:attribute).only_integer`
+
+* Add a `query_the_database` matcher:
+
+    `it { should query_the_database(4.times).when_calling(:complicated_method) }`
+    `it { should query_the_database(4.times).or_less.when_calling(:complicated_method) }`
+    `it { should_not query_the_database.when_calling(:complicated_method) }`
+
+* Database columns are now correctly checked for primality. E.G., this works
+  now: `it { should have_db_column(:id).with_options(:primary => true) }`
+
+* The flash matcher can check specific flash keys using [], like so:
+  `it { should set_the_flash[:alert].to("Password doesn't match") }`
+
+* The `have_sent_email` matcher can check `reply_to`:
+  ` it { should have_sent_email.reply_to([user, other]) }`
+
+* Add `validates_confirmation_of` matcher:
+  `it { should validate_confirmation_of(:password) }`
+
+* Add `serialize` matcher:
+  `it { should serialize(:details).as(Hash).as_instance_of(Hash) }`
+
+* shoulda-matchers checks for all possible I18n keys, instead of just
+  e.g. `activerecord.errors.messages.blank`
+
+* Add `accept_nested_attributes` matcher
+
+* Our very first dependency: ActiveSupport >= 3.0.0