kotovalexarian-likes-github
/
thoughtbot--shoulda-matchers
mirror of https://github.com/thoughtbot/shoulda-matchers.git
1
0
Fork 0
Code Releases Activity
thoughtbot--shoulda-matchers/lib/shoulda/matchers/active_record.rb

25 lines
1.3 KiB
Ruby
Raw Normal View History

Move into the Matchers namespace
2010-12-15 22:34:19 +00:00
require 'shoulda/matchers/active_record/association_matcher'
Extract examples in README to inline documentation
2014-01-23 18:07:36 +00:00
require 'shoulda/matchers/active_record/association_matchers'
Add support for counter_cache option in belongs_to associations
2013-06-19 23:52:46 +00:00
require 'shoulda/matchers/active_record/association_matchers/counter_cache_matcher'
+ Add inverse of matcher for active record association
2014-03-19 03:13:28 +00:00
require 'shoulda/matchers/active_record/association_matchers/inverse_of_matcher'
Check correct columns are present in join table The `have_and_belong_to_many` matcher could give a false positive if the join table is present but does not contain the correct columns. Check to see if the columns exist in the join table and provide a meaningful failure message if one or more of the columns are not present.
2014-04-26 05:26:45 +00:00
require 'shoulda/matchers/active_record/association_matchers/join_table_matcher'
Extract submatchers from AssociationMatcher Refactored AssociationMatcher so that `#order`, `#through`, and `#dependent` would be their own submatchers. This reduces some of the clutter in the main class, especially as we continue expanding it. In addition, a few related tests were modified so that they would check failure messages also.
2013-06-07 14:14:27 +00:00
require 'shoulda/matchers/active_record/association_matchers/order_matcher'
require 'shoulda/matchers/active_record/association_matchers/through_matcher'
require 'shoulda/matchers/active_record/association_matchers/dependent_matcher'
Association matchers now support :source option
2013-11-27 18:18:46 +00:00
require 'shoulda/matchers/active_record/association_matchers/source_matcher'
Extract submatchers from AssociationMatcher Refactored AssociationMatcher so that `#order`, `#through`, and `#dependent` would be their own submatchers. This reduces some of the clutter in the main class, especially as we continue expanding it. In addition, a few related tests were modified so that they would check failure messages also.
2013-06-07 14:14:27 +00:00
require 'shoulda/matchers/active_record/association_matchers/model_reflector'
Fix converting association options to a Relation Under Rails 3 when using an association matcher in conjunction with a submatcher such as #order, we have to take the options on the association (:conditions, :order, etc.) and convert them to an ActiveRecord::Relation object. This happens in ModelReflector. Unfortunately, converting an :includes option was broken. This is in part due to ModelReflector not having proper tests, but also, the method that does the conversion to Relation is rather complex and could be broken up so it can be tested better. In fact I noticed that there's a lot of stuff in ModelReflector that does stuff around a Reflection object, so it would be better to define a ModelReflection class that simply decorates a Reflection. That's what I've done and also added proper tests.
2013-10-21 00:41:30 +00:00
require 'shoulda/matchers/active_record/association_matchers/model_reflection'
Refactor AssociationMatcher to use new OptionVerifier When using an association matcher you may have qualifiers on that matcher which let you make assertions on options passed to the association method that you are testing. For instance, has_many has a :dependent option and so in order to test this you say something like it { should have_many(:people).dependent(:destroy) } In order to test such an option we have to compare the option you passed with what the actual value of that option is. This is usually obtained by looking at the reflection object of the association in question, although it can be obtained by other means too. Anyway, the code that does this comparison isn't terrible, but there are two problems with it. First, it involves typecasting both expected and actual values. For instance, this: has_many :people, dependent: :destroy it { should have_many(:people).dependent(:destroy) } should be equivalent to: has_many :people, dependent: :destroy it { should have_many(:people).dependent('destroy') } should be equivalent to: has_many :people, dependent: 'destroy' it { should have_many(:people).dependent(:destroy) } Second, we are a little screwed if the method of obtaining the actual value of the option changes depending on which Rails version you're using. So, OptionVerifier attempts to address both of these issues. It's a little crazy, but it works. I also moved some methods from AssociationMatcher to ModelReflector where they really belong.
2013-08-16 21:38:10 +00:00
require 'shoulda/matchers/active_record/association_matchers/option_verifier'
Move into the Matchers namespace
2010-12-15 22:34:19 +00:00
require 'shoulda/matchers/active_record/have_db_column_matcher'
require 'shoulda/matchers/active_record/have_db_index_matcher'
require 'shoulda/matchers/active_record/have_readonly_attribute_matcher'
Adds the serialize matcher to ActiveRecord matchers.
2011-11-15 22:11:41 +00:00
require 'shoulda/matchers/active_record/serialize_matcher'
Adds accept_nested_attributes_for matcher Currently supports the options "allow_destroy", "limit", and "update_only"
2012-04-11 18:33:21 +00:00
require 'shoulda/matchers/active_record/accept_nested_attributes_for_matcher'
Move into the Matchers namespace
2010-12-15 22:34:19 +00:00
module Shoulda
module Matchers
module ActiveRecord
end
end
end