…ttribute has other validations on it. Now that the upper bound matchers are not being skipped for the is_equal_to case, the expected error message needs to be set for the upper bound.
…he home of the join table using the parent model. This allows developers to define HABTM relationships in other databases and still use the 'have_and_belong_to_many' matcher.
Currently, there is an assumption that `matched_index.unique` will be `true` and not truthy. This is not always the case. This can cause tests to fail, even though they should pass. This allows `matched_index.unique` to be truthy.
* Replaces repeated conditional with polymorphism
* Checks for exceptions raised from #validates! and :strict => true
An edge case occurs 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] . Work around this by always inserting the shoulda matchers into Test::Unit, regardless of whether RSpec is loaded.