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/spec/unit_spec_helper.rb

55 lines
1.9 KiB
Ruby
Raw Normal View History

Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb
2015-11-30 01:57:45 +00:00
require_relative 'support/unit/load_environment'
Extracted the context framework, switched to rspec
2010-12-13 22:28:59 +00:00
Rearrange requires.
2012-03-24 01:00:36 +00:00
require 'rspec/rails'
Fix inclusion to correctly disallow outside values The inclusion matcher, when qualified with `in_array`, was using AllowValueMatcher to check that values outside the array were disallowed by the model (and then inverting its result). However, it should have been using DisallowValueMatcher all this time. This commit fixes that. Without this fix, the following error is raised when using the inclusion matcher against a model which does not have the proper inclusion validation on it: undefined method `attribute_setter' for nil:NilClass This happens because the inclusion matcher is a complex matcher, i.e., it runs a series of submatchers internally and the result of those submatchers contributes to whether or not the matcher matches. If one of those submatchers fails, the inclusion matcher immediately fails and spits out the failure message associated with that submatcher. However, there is a fundamental difference between AllowValueMatcher and DisallowValueMatcher as it relates to how they function: * AllowValueMatcher sets an attribute to a value on a record and expects the record not to fail validation. * DisallowValueMatcher sets an attribute to a value on a record, but expects the record *to* fail validation. The issue in this case is that, because AllowValueMatcher was used instead of DisallowValueMatcher, the inclusion matcher thought that the AllowValueMatcher failed, when in fact it passed (this result was just inverted). So it tried to generate a failure message for a matcher that didn't fail in the first place. By using DisallowValueMatcher, we set the proper expectations.
2018-09-12 05:05:06 +00:00
require 'rspec/matchers/fail_matchers'
Ensure that we are req'd after rspec in tests Currently before running unit tests we are getting auto-required before rspec-rails is getting required. This is bad because we need to wait until rspec-rails is loaded before injecting Shoulda::Matchers::* into the current RSpec context, otherwise matchers that clash with rspec-rails (such as `render_template` will get overridden). This is happening when creating and booting the Rails application. Bundler will auto-require any gems in the Gemfile. One of these gems is ourselves (via the `gemspec` line). Since there aren't any dependencies in the gemspec, there's no need for us to be in the Gemfile. This means that we no longer have to explicit `include` Rails ActionController template assertions in the tests for `render_template` as they should get included automatically for us.
2014-12-24 21:28:35 +00:00
require 'shoulda-matchers'
Extracted the context framework, switched to rspec
2010-12-13 22:28:59 +00:00
Extract a common spec helper In order to write tests for the `word_wrap` method we have, we need a spec helper that we can require. We don't need anything fancy. The doublespeak_spec_helper is doing most of what we want except for the Doublespeak require.
2015-10-07 17:09:59 +00:00
require 'spec_helper'
Extracted the context framework, switched to rspec
2010-12-13 22:28:59 +00:00
Add new RSpec acceptance tests to replace Cucumber
2014-10-27 00:52:55 +00:00
Dir[ File.join(File.expand_path('../support/unit/**/*.rb', __FILE__)) ].sort.each do |file|
Reorganize unit tests, part II * Change 'spec' Rake task to 'spec:unit' * Require unit_spec_helper.rb in unit tests, not spec_helper.rb * Re-namespace files in spec/support/unit under UnitTests * Files in spec/support/unit/helpers no longer automatically add themselves to RSpec - this happens in unit_spec_helper.rb * Extract RecordWithDifferentErrorAttributeBuilder and RecordValidatingConfirmationBuilder to separate files
2014-10-27 00:51:42 +00:00
require file
end
Extracted the context framework, switched to rspec
2010-12-13 22:28:59 +00:00
RSpec.configure do |config|
Fix inclusion to correctly disallow outside values The inclusion matcher, when qualified with `in_array`, was using AllowValueMatcher to check that values outside the array were disallowed by the model (and then inverting its result). However, it should have been using DisallowValueMatcher all this time. This commit fixes that. Without this fix, the following error is raised when using the inclusion matcher against a model which does not have the proper inclusion validation on it: undefined method `attribute_setter' for nil:NilClass This happens because the inclusion matcher is a complex matcher, i.e., it runs a series of submatchers internally and the result of those submatchers contributes to whether or not the matcher matches. If one of those submatchers fails, the inclusion matcher immediately fails and spits out the failure message associated with that submatcher. However, there is a fundamental difference between AllowValueMatcher and DisallowValueMatcher as it relates to how they function: * AllowValueMatcher sets an attribute to a value on a record and expects the record not to fail validation. * DisallowValueMatcher sets an attribute to a value on a record, but expects the record *to* fail validation. The issue in this case is that, because AllowValueMatcher was used instead of DisallowValueMatcher, the inclusion matcher thought that the AllowValueMatcher failed, when in fact it passed (this result was just inverted). So it tried to generate a failure message for a matcher that didn't fail in the first place. By using DisallowValueMatcher, we set the proper expectations.
2018-09-12 05:05:06 +00:00
config.include RSpec::Matchers::FailMatchers
Scope request parameters according to Rails version
2017-01-09 12:31:46 +00:00
UnitTests::ActionPackVersions.configure_example_group(config)
Reorganize unit tests, part II * Change 'spec' Rake task to 'spec:unit' * Require unit_spec_helper.rb in unit tests, not spec_helper.rb * Re-namespace files in spec/support/unit under UnitTests * Files in spec/support/unit/helpers no longer automatically add themselves to RSpec - this happens in unit_spec_helper.rb * Extract RecordWithDifferentErrorAttributeBuilder and RecordValidatingConfirmationBuilder to separate files
2014-10-27 00:51:42 +00:00
UnitTests::ActiveModelHelpers.configure_example_group(config)
UnitTests::ActiveModelVersions.configure_example_group(config)
UnitTests::ClassBuilder.configure_example_group(config)
UnitTests::ControllerBuilder.configure_example_group(config)
UnitTests::I18nFaker.configure_example_group(config)
UnitTests::MailerBuilder.configure_example_group(config)
UnitTests::ModelBuilder.configure_example_group(config)
UnitTests::RailsVersions.configure_example_group(config)
Handle RangeErrors emitted now in ActiveRecord 4.2 In Rails 4.2, ActiveRecord was changed such that if you attempt to set an attribute to a value and that value is outside the range of the column, then it will raise a RangeError. For instance, an integer column with a limit of 2 (i.e. a smallint) only accepts values between -32768 and +32767. This means that if you try to do any of these three things, a RangeError could be raised: * Use validate_numericality_of along with any of the comparison submatchers and a value that sits on either side of the boundary. * Use allow_value with a value that sits outside the range. * Use validates_inclusion_of against an integer column. (Here we attempt to set that column to a non-integer value to verify that the attribute does not allow said value. That value is really a string version of a large number, so if the column does not take large numbers then the matcher could blow up.) Ancillary changes in this commit: * Remove ValidationMessageFinder and ExceptionMessageFinder in favor of Validator, StrictValidator, and ValidatorWithCapturedRangeError. * The allow_value matcher now uses an instance of Validator under the hood. StrictValidator and/or ValidatorWithCapturedRangeError may be mixed into the Validator object as needed.
2015-01-21 22:46:26 +00:00
UnitTests::ActiveRecordVersions.configure_example_group(config)
UnitTests::ActiveModelVersions.configure_example_group(config)
Add support for Postgres When running tests, you can now switch between running them against a SQLite or PostgreSQL database. This is accomplished by modifying the unit and acceptance tests so that when they generate and load the test Rails application, database.yml is replaced with content that will configure the database appropriately.
2015-02-08 21:38:55 +00:00
UnitTests::DatabaseHelpers.configure_example_group(config)
UnitTests::ColumnTypeHelpers.configure_example_group(config)
Add ValidationMatcherScenario for use in tests Also add a helper method, `build_scenario_for_validation_matcher`, to all unit tests. Our plan is to slowly transition all of the tests to use this helper method, and that we we can get rid of the umpteen different ways we are building records across all of the tests.
2015-12-27 05:55:06 +00:00
UnitTests::ValidationMatcherScenarioHelpers.configure_example_group(config)
Improve failure messages for define_enum_for If a subtest fails, explain why. We're going to be adding another subtest later, and so without this extra information, users will most definitely be confused.
2018-01-26 19:33:27 +00:00
UnitTests::MessageHelpers.configure_example_group(config)
Reorganize unit tests, part II * Change 'spec' Rake task to 'spec:unit' * Require unit_spec_helper.rb in unit tests, not spec_helper.rb * Re-namespace files in spec/support/unit under UnitTests * Files in spec/support/unit/helpers no longer automatically add themselves to RSpec - this happens in unit_spec_helper.rb * Extract RecordWithDifferentErrorAttributeBuilder and RecordValidatingConfirmationBuilder to separate files
2014-10-27 00:51:42 +00:00
Don't require ActiveResource tests under Rails 5
2016-09-04 03:35:13 +00:00
if UnitTests::RailsVersions.rails_lte_4?
UnitTests::ActiveResourceBuilder.configure_example_group(config)
end
Reorganize unit tests, part II * Change 'spec' Rake task to 'spec:unit' * Require unit_spec_helper.rb in unit tests, not spec_helper.rb * Re-namespace files in spec/support/unit under UnitTests * Files in spec/support/unit/helpers no longer automatically add themselves to RSpec - this happens in unit_spec_helper.rb * Extract RecordWithDifferentErrorAttributeBuilder and RecordValidatingConfirmationBuilder to separate files
2014-10-27 00:51:42 +00:00
config.include UnitTests::Matchers
Add 'it supports' as an alias for 'it behaves like' Oftentimes our shared example groups represent tests for qualifiers. It's more natural to say "it supports ignoring_interference_by_writer" instead of "it behaves like it supports ignoring_interference_by_writer".
2015-12-24 20:05:26 +00:00
config.infer_spec_type_from_file_location!
config.example_status_persistence_file_path = "spec/examples.txt"
config.alias_it_behaves_like_to(:it_supports, "it supports")
config.before(:all, type: :controller) do
self.class.controller(ApplicationController) { }
end
Extracted the context framework, switched to rspec
2010-12-13 22:28:59 +00:00
end
Remove all Ruby-emitted warnings Run RSpec tests with warnings enabled so we stay on top of this better in the future.
2014-06-27 22:39:39 +00:00
Ensure that ActiveSupport warnings are being printed during tests
2014-12-24 21:46:10 +00:00
ActiveSupport::Deprecation.behavior = :stderr
Remove auto-detection of Rails / test framework
2014-10-23 00:54:36 +00:00
Shoulda::Matchers.configure do |config|
config.integrate do |with|
with.test_framework :rspec
with.library :rails
end
end