kotovalexarian-likes-github/thoughtbot--shoulda-matchers
1
0
Fork 0
mirror of https://github.com/thoughtbot/shoulda-matchers.git synced 2022-11-09 12:01:38 -05:00
Code Releases Activity
thoughtbot--shoulda-matchers/spec/unit_spec_helper.rb

59 lines
1.7 KiB
Ruby
Raw Normal View History

Raise an error if no Appraisal is specified If you attempt to run tests without specifying an Appraisal, then you will be going off of the main Gemfile. The Gemfile is not guaranteed to contain all of the dependencies necessary to run tests, so it is very likely that you'll get an obscure error somewhere. Instead of letting this happen, raise a specific error.
2015-02-05 20:03:32 -05:00
require_relative 'support/tests/current_bundle'
Tests::CurrentBundle.instance.assert_appraisal!
#---
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-26 20:51:42 -04:00
require File.expand_path('../support/unit/rails_application', __FILE__)
Auto-retry `bundle install` when Travis runs tests `bundle install` doesn't always work -- sometimes it runs into errors making HTTP requests, for whatever reason. This will cause Travis to fail which is pretty annoying. * Travis supplies an executable called `travis_retry` which will automatically retry the command up to 3 times before really failing. Tell Travis to use this when it runs `bundle install` before it runs tests. * In spec_helper, we create a Rails app and use this within the test suite. This will also run `bundle install`. Unfortunately we can't use `travis_retry` for this as it's a function and is not available to us in Ruby-land, so use our own retry logic.
2013-10-23 16:18:52 -04:00
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-26 20:51:42 -04:00
$test_app = UnitTests::RailsApplication.new
Refactor spec_helper The code that sets up the blank Rails application we use for testing is a little messy. Let's use an object to encapsulate this and then refer to this object every time we access Rails.application.
2013-11-22 22:25:27 -05:00
$test_app.create
$test_app.load
Extracted the context framework, switched to rspec
2010-12-13 17:28:59 -05:00
Refactor spec_helper The code that sets up the blank Rails application we use for testing is a little messy. Let's use an object to encapsulate this and then refer to this object every time we access Rails.application.
2013-11-22 22:25:27 -05:00
ENV['BUNDLE_GEMFILE'] ||= app.gemfile_path
Auto-retry `bundle install` when Travis runs tests `bundle install` doesn't always work -- sometimes it runs into errors making HTTP requests, for whatever reason. This will cause Travis to fail which is pretty annoying. * Travis supplies an executable called `travis_retry` which will automatically retry the command up to 3 times before really failing. Tell Travis to use this when it runs `bundle install` before it runs tests. * In spec_helper, we create a Rails app and use this within the test suite. This will also run `bundle install`. Unfortunately we can't use `travis_retry` for this as it's a function and is not available to us in Ruby-land, so use our own retry logic.
2013-10-23 16:18:52 -04:00
ENV['RAILS_ENV'] = 'test'
Extracted the context framework, switched to rspec
2010-12-13 17:28:59 -05:00
Rearrange requires.
2012-03-23 21:00:36 -04:00
require 'rspec/rails'
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 16:28:35 -05:00
require 'shoulda-matchers'
Extracted the context framework, switched to rspec
2010-12-13 17:28:59 -05: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 13:09:59 -04:00
require 'spec_helper'
Extracted the context framework, switched to rspec
2010-12-13 17:28:59 -05:00
Add new RSpec acceptance tests to replace Cucumber
2014-10-26 20:52:55 -04: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-26 20:51:42 -04:00
require file
end
Extracted the context framework, switched to rspec
2010-12-13 17:28:59 -05:00
RSpec.configure do |config|
Remove warning from RSpec RSpec 3 will no longer infer the spec type from the file location, so 2.99 prints this warning: -------------------------------------------------------------------------------- rspec-rails 3 will no longer automatically infer an example group's spec type from the file location. You can explicitly opt-in to this feature using this snippet: RSpec.configure do |config| config.infer_spec_type_from_file_location! end If you wish to manually label spec types via metadata you can safely ignore this warning and continue upgrading to RSpec 3 without addressing it. -------------------------------------------------------------------------------- So this commit merely adds the snippet to get rid of that warning.
2014-10-17 14:27:53 -04:00
if config.respond_to?(:infer_spec_type_from_file_location!)
config.infer_spec_type_from_file_location!
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-26 20:51:42 -04:00
Fix AC matcher tests for Rails 4.2 Modify helper methods provided by ControllerBuilder so that we use as much of rspec-rails's controller example group capabilities as possible. All of this can still be improved but this is a good start for now.
2014-12-24 16:44:38 -05:00
config.before(:all, type: :controller) do
self.class.controller(ApplicationController) { }
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-26 20:51:42 -04:00
UnitTests::ActiveModelHelpers.configure_example_group(config)
UnitTests::ActiveModelVersions.configure_example_group(config)
UnitTests::ActiveResourceBuilder.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 17:46:26 -05: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 16:38:55 -05:00
UnitTests::DatabaseHelpers.configure_example_group(config)
UnitTests::ColumnTypeHelpers.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-26 20:51:42 -04:00
config.include UnitTests::Matchers
Extracted the context framework, switched to rspec
2010-12-13 17:28:59 -05: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 18:39:39 -04:00
Ensure that ActiveSupport warnings are being printed during tests
2014-12-24 16:46:10 -05:00
ActiveSupport::Deprecation.behavior = :stderr
Remove auto-detection of Rails / test framework
2014-10-22 20:54:36 -04:00
Shoulda::Matchers.configure do |config|
config.integrate do |with|
with.test_framework :rspec
with.library :rails
end
end
Copy permalink