File rubygem-shoulda-matchers.changes of Package rubygem-shoulda-matchers
-------------------------------------------------------------------
Tue Feb 10 18:33:19 UTC 2015 - coolo@suse.com
- updated to version 2.8.0
-------------------------------------------------------------------
Mon Oct 13 18:46:02 UTC 2014 - coolo@suse.com
- adapt to new rubygem packaging
-------------------------------------------------------------------
Sun May 18 09:04:42 UTC 2014 - coolo@suse.com
- updated to version 2.6.1
## Features
* Teach `with_message` qualifier on `allow_value` to accept a hash of i18n
interpolation values:
`allow_value('foo').for(:attr).with_message(:greater_than, values: { count: 20 })`.
## Bug fixes
* Revert changes to `validate_numericality_of` made in the last release, which
made it so that comparison qualifiers specified on the validation are tested
using a very small decimal number offset rather than a whole number by
default, except if the matcher was qualified with `only_integer`. This means
that prior to 2.6.0, if your validation specified `only_integer` and you did
not, then after 2.6.0 that test would fail. This is now fixed.
* Fix regression in previous release where ActiveRecord matchers would not be
included when ActiveRecord wasn't defined (i.e. if you were using ActiveModel
only).
* Revert the behavior of `allow_value` changed in 2.6.0 (it will no longer raise
CouldNotClearAttribute). This was originally done as a part of a fix for
`validate_presence_of` when used in conjunction with `has_secure_password`.
That fix has been updated so that it does not affect `allow_value`.
* Fix callback matchers and correct test coverage.
* Fix `permit` so that it does not interfere with different usages of `params`
in your controller action. Specifically, this will not raise an error:
`params.fetch(:foo, {}).permit(:bar, :baz)` (the `permit` will have no
problems recognizing that :bar and :baz are permitted params).
* Fix `permit` on Rails 4.1 to use PATCH by default for #update instead of PUT.
Previously you had to specify this manually.
* Fix `permit` so that it track multiple calls to #permit in your controller
action. Previously only the last usage of #permit would be considered in
determining whether the matcher matched.
* Fix `permit` so that if the route for your action requires params (such as id)
then you can now specify those params:
`permit(:first_name, :last_name).for(:update, params: { id: 42 })`.
* Fix `delegate_method` so that it does not stub the target method forever,
returning it to its original implementation after the match ends.
* Fix `validate_uniqueness_of` to work with Rails 4.1 enum columns.
# 2.6.0
* The boolean argument to `have_db_index`'s `unique` option is now optional, for
consistency with other matchers.
* 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.
-------------------------------------------------------------------
Mon Jan 20 09:29:00 UTC 2014 - coolo@suse.com
- updated to version 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.
-------------------------------------------------------------------
Thu Oct 10 14:20:48 UTC 2013 - coolo@suse.com
- updated to version 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).
-------------------------------------------------------------------
Mon Aug 26 05:05:52 UTC 2013 - coolo@suse.com
- updated to version 2.3.0
-------------------------------------------------------------------
Thu Jun 13 05:22:58 UTC 2013 - coolo@suse.com
- updated to version 2.2.0
-------------------------------------------------------------------
Thu May 9 17:40:41 UTC 2013 - coolo@suse.com
- updated to version 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.
-------------------------------------------------------------------
Sun Apr 14 08:28:54 UTC 2013 - coolo@suse.com
- updated to version 2.0.0
-------------------------------------------------------------------
Wed Mar 20 06:15:31 UTC 2013 - coolo@suse.com
- updated to version 1.5.2
* Bump version depedency of Bourne to allow for Mocha upgrade.
* Should fix incompatiblity with MiniTest.
-------------------------------------------------------------------
Tue Mar 19 19:50:16 UTC 2013 - coolo@suse.com
- fix permissions
-------------------------------------------------------------------
Mon Mar 18 13:01:20 UTC 2013 - coolo@suse.com
- updated to version 1.5.0
-------------------------------------------------------------------
Sat Dec 1 14:19:26 UTC 2012 - coolo@suse.com
- updated to version 1.4.2
* Added a new delegate_method matcher.
-------------------------------------------------------------------
Sun Oct 28 05:58:39 UTC 2012 - coolo@suse.com
- updated to version 1.4.1
-------------------------------------------------------------------
Tue Oct 9 08:31:39 UTC 2012 - coolo@suse.com
- updated to version 1.4.0
-------------------------------------------------------------------
Sun Sep 2 10:36:13 UTC 2012 - coolo@suse.com
- updated to version 1.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"`.
-------------------------------------------------------------------
Mon Jul 30 19:08:03 UTC 2012 - coolo@suse.com
- initial package
