All Versions
47
Latest Version
Avg Release Cycle
139 days
Latest Release
1082 days ago

Changelog History
Page 2

  • v4.1.2 Changes

    August 01, 2019

    🐛 Bug fixes

    • Fix another regression with validate_presence_of so that it works against an attribute that has been decorated with serialize using a custom serializer class. (#1236)

  • v4.1.1 Changes

    July 16, 2019

    🐛 Bug fixes

    • Patch some backward-incompatible changes to validate_presence_of that were made in the last version. As of 4.1.0 the presence matcher now checks to ensure that empty string will cause the record to be invalid (in addition to nil, which it was already checking against). However, this check was being performed even if the attribute or column the presence matcher is being run against didn't support being set to an empty string. This releases fixes this. (#1222, #1224, #1231)

  • v4.1.0 Changes

    July 16, 2019

    🐛 Bug fixes

    • Fix validate_uniqueness_of so that it works when a scope is defined as a string instead of a symbol on the model. (#1176)

    • Fix have_db_index so that it can be used against multiple models that are connected to different databases. (#1200)

    🔋 Features

    • ➕ Add support for Rails 6. No new Rails 6 features are supported, but only existing features that broke with the upgrade. (#1193)

    • ➕ Add support for expression indexes (Rails 5, Postgres only) to have_db_index. (#1211)

    • Add allow_nil to the validate_presence_of matcher. (834d8d0, #1100)

    👌 Improvements

    • Update validate_presence_of so that if it is being used against an association which is required: true or optional: false, or it is not configured as such but ActiveRecord defaults belong_to associations to optional: false, and the matcher fails, the developer is reminded in the failure message that the belong_to matcher can be used instead. (#1214, 8697b01)

    • Update define_enum_for so that it produces a more helpful message on failure. (#1216)

  • v4.0.1 Changes

    February 26, 2019

    🐛 Bug fixes

    • 🛠 Fix gemspec so that setup script isn't installed globally when gem is installed. (#1180)

  • v4.0.0 Changes

    February 22, 2019

    🚀 This release mainly brings the gem up to date with modern versions of Ruby and 🚅 Rails and drops support for older, unsupported versions. The compatibility list is now:

    • 💎 Ruby: 2.6.0, 2.5.1, 2.4.4, 2.3.7
    • 🚅 Rails: 5.2.2, 5.1.6.1, 5.0.7, 4.2.10

    Backward-incompatible changes

    • ⬇️ Drop support for Rails 4.0 and 4.1 as well as Ruby 2.0, 2.1, and 2.2, since they've been end-of-lifed. The gem now supports Ruby 2.3+ and Rails 4.2+.

    • use_before_filter, use_after_filter, and use_around_filter are no longer usable when using shoulda-matchers under Rails 5.x, as the corresponding controller callbacks don't exist there. (#1054)

    🗄 Deprecations

    • define_enum_for: with is deprecated in favor of with_values. This is to prevent confusion with with_prefix and with_suffix, which are new. (#1077)

    🐛 Bug fixes

    • 🛠 Fix association matchers when used under Rails 5.x so that they make use of ActiveRecord::Base.connection.data_sources instead of ActiveRecord::Base.connection.tables, which was deprecated. (#933, #943, 61c3654)

    • 🛠 Fix the serialize matcher so that it works with Rails 5.x. (#913, #965, df04f87)

    • 🛠 Fix our custom mocking library Doublespeak, which is used by delegate_method, so that it does not produce a warning under Ruby 2.4. ([#1006], #1038, 8d7dcb8)

    • 🛠 Fix the permit matcher so that it uses the correct method signature to call the controller action with params in order to prevent a warning under Rails 5.x. (#867, #917, #964, #989, ce9624b)

    • Fix the define_enum_for matcher so that it once more allows string columns to be used as enum attributes. (#912, #1063, 5650aae)

    • Fix validate_uniqueness_of when used under Rails 4.2 so that when the attribute you're testing is a boolean column, it will no longer emit a warning. (#949, #1073)

    • Fix validate_inclusion_of so that if it fails, it will no longer blow up with the error "undefined method `attribute_setter' for nil:NilClass". (#904)

    • ➕ Add negative versions of all validation matchers (i.e. implement does_not_match? for them) to prevent them from blowing up with "undefined method `attribute_setter' for nil:NilClass". (#904)

    🔋 Features

    • Add required and optional qualifiers to belong_to and have_one matchers. (When using the belong_to matcher under Rails 5+, required is assumed unless overridden.) (#861, #870, #956, 3af3d9f)

    • Add without_validating_presence qualifier to belong_to to get around the fact that required is assumed, above. (#1153, #1154)

    • Add allow_nil qualifier to delegate_method. (#798, d49cfca)

    • Add allow_nil qualifier to validate_length_of. (#724)

    • ➕ Add a port option to the route matcher to allow testing a route that has a constraint on it such that only a specific port may be used to access that route. (#954, #1074, #1075)

    • Add with_prefix and with_suffix to define_enum_for to allow testing the enum macro with corresponding prefix and suffix options (Rails 5 only). (#961, #1077)

    • Add index_errors option to has_many (Rails 5 only). (#1089, 795ca68)

    👌 Improvements

  • v4.0.0.rc1 Changes

    October 02, 2018

    ➕ Adds support for Ruby 2.4 and 2.5 and Rails 5.x.
    ⬇️ Drops support for Ruby 2.0 and 2.1 as well as Rails 4.0 and 4.1.

  • v3.1.3 Changes

    January 29, 2019

    👌 Improvements

    • ⚡️ Update BigDecimal.new() to use BigDecimal() and avoid deprecation warnings in Ruby 2.6.

  • v3.1.2 Changes

    July 12, 2017

    🗄 Deprecations

    • This is the last version that supports Rails 4.0 and 4.1 and Ruby 2.0 and 2.1.

    🐛 Bug fixes

    • When the permit matcher was used without #on, the controller did not use params#require, the params object was duplicated, and the matcher did not recognize the #permit call inside the controller. This behavior happened because the matcher overwrote double registries with the same parameter hash whenever ActionController::Parameters was instantiated. (#899, #902, 44c019)

  • v3.1.1 Changes

    January 28, 2016

    🐛 Bug fixes

    • 👍 Some matchers make use of ActiveSupport's in? method, but do not include the file where this is defined in ActiveSupport. This causes problems with projects using shoulda-matchers that do not include all of ActiveSupport by default. To fix this, replace in? with Ruby's builtin include?. (#879)

    • validate_uniqueness_of works by creating a record if it doesn't exist, and then testing against a new record with various attributes set that are equal to (or different than) corresponding attributes in the existing record. In 3.1.0 a change was made whereby when the uniqueness matcher is given a new record and creates an existing record out of it, it ensures that the record is valid before continuing on. This created a problem because if the subject, before it was saved, was empty and therefore in an invalid state, it could not effectively be saved. While ideally this should be enforced, doing so would be a backward-incompatible change, so this behavior has been rolled back. (#880, #884, #885, 45de869)

    • Fix an issue with validate_uniqueness_of + scoped_to when used against a model where the attribute has multiple uniqueness validations and each validation has a different set of scopes. In this case, a test written for the first validation (and its scopes) would pass, but tests for the other validations (and their scopes) would not, as the matcher only considered the first set of scopes as the actual set of scopes. (#830, 28bd9a1)

    👌 Improvements

    • Update validate_uniqueness_of so that if an existing record fails to be created because a column is non-nullable and was not filled in, raise an ExistingRecordInvalid exception with details on how to fix the test. (78ccfc5)

  • v3.1.0 Changes

    January 11, 2016

    🐛 Bug fixes

    • Update validate_numericality_of so that submatchers are applied lazily instead of immediately. Previously, qualifiers were order-dependent, meaning that if you used strict before you used, say, odd, then strict wouldn't actually apply to odd. Now the order that you specify qualifiers doesn't matter. (6c67a5e)

    • 🛠 Fix allow_value so that it does not raise an AttributeChangedValueError (formerly CouldNotSetAttributeError) when used against an attribute that is an enum in an ActiveRecord model. (9e8603e)

    • Add a ignoring_interference_by_writer qualifier to all matchers, not just allow_value. This is enabled by default, which means that you should never get a CouldNotSetAttributeError again. (You may get some more information if a test fails, however.) (#786, #799, #801, #804, #817, #841, #849, #872, #873, #874, 1189934, 5532f43)

    • Fix validate_numericality_of so that it does not blow up when used against a virtual attribute defined in an ActiveRecord model (that is, an attribute that is not present in the database but is defined using attr_accessor). (#822)

    • Update validate_numericality_of so that it no longer raises an IneffectiveTestError if used against a numeric column. (#832, 5ed0362)

    🔋 Features

    • Add a new qualifier, ignoring_case_sensitivity, to validate_uniqueness_of. This provides a way to test uniqueness of an attribute whose case is normalized, either in a custom writer method for that attribute, or in a custom before_validation callback. (#836, #840)

    👌 Improvements

    • 👌 Improve failure messages and descriptions of all matchers across the board so that it is easier to understand what the matcher was doing when it failed. (You'll see a huge difference in the output of the numericality and uniqueness matchers in particular.)

    • Matchers now raise an error if any attributes that the matcher is attempting to set do not exist on the model. (2962112)

    • Update validate_numericality_of so that it doesn't always run all of the submatchers, but stops on the first one that fails. Since failure messages now contain information as to what value the matcher set on the attribute when it failed, this change guarantees that the correct value will be shown. (8e24a6e)

    • Continue to detect if attributes change incoming values, but now instead of immediately seeing a CouldNotSetAttributeError, you will only be informed about it if the test you've written fails. (1189934)

    • Add an additional check to define_enum_for to ensure that the column that underlies the enum attribute you're testing is an integer column. (68dd70a)

    • Add a test for validate_numericality_of so that it officially supports money columns. (#841, a559713)