Elliot Winkler 8fa97b4ff3 Fix inclusion matcher w/ date & datetime attrs ... Why: * The inclusion matcher (when used with the `in_array` qualifier) makes the assertion that when the attribute is set to a value that is outside the given array, the record in question is invalid. The issue is that when used with a date or datetime attribute, the arbitrary value the matcher chose was a string. This was getting typecast and so the matcher was throwing a CouldNotSetAttributeError. To satisfy the above: * If the column is a date, use a Date for the arbitrary value * If the column is a datetime, use a DateTime for the arbitrary value * If the column is a time, use a Time for the arbitrary value		2015-10-04 16:55:48 -06:00
..
acceptance	Make independent matchers really independent	2015-10-01 10:12:17 -06:00
support	Make independent matchers really independent	2015-10-01 10:12:17 -06:00
unit/shoulda/matchers	Fix inclusion matcher w/ date & datetime attrs	2015-10-04 16:55:48 -06:00
warnings_spy	Be better about looking for warnings on Travis	2014-12-16 20:30:05 -07:00
acceptance_spec_helper.rb	Use pry-byebug instead of pry-nav	2015-04-02 20:13:33 -06:00
doublespeak_spec_helper.rb	Use doc formatter when running Doublespeak tests	2015-09-29 18:42:08 -06:00
report_warnings.rb	Remove all Ruby-emitted warnings	2014-07-18 18:00:08 -06:00
unit_spec_helper.rb	Run formatter documentation when running a single file	2015-06-13 10:37:31 -03:00
warnings_spy.rb	Fail build if there are warnings	2015-02-09 10:48:49 -07:00