trabajo-afectivo/spec/models/group_spec.rb

require 'rails_helper'
require 'models/application_model_examples'
require 'models/concerns/can_be_imported_examples'
require 'models/concerns/has_object_manager_attributes_validation_examples'

RSpec.describe Group, type: :model do
  it_behaves_like 'ApplicationModel'
  it_behaves_like 'CanBeImported'
  it_behaves_like 'HasObjectManagerAttributesValidation'
end
Refactoring: Migrate ApplicationModel::ChecksImport part of db_auto_increment_test.rb to RSpec 2019-01-22 16:35:01 +00:00			`require 'rails_helper'`
			`require 'models/application_model_examples'`
Refactoring: Eliminate explicit coupling of classes in ChecksImport concern 2019-01-28 06:04:05 +00:00			`require 'models/concerns/can_be_imported_examples'`
Fixed issues #1259 and #1598 by adding ObjectManager::Attribute validations. 2019-03-13 23:51:22 +00:00			`require 'models/concerns/has_object_manager_attributes_validation_examples'`
Refactoring: Migrate ApplicationModel::ChecksImport part of db_auto_increment_test.rb to RSpec 2019-01-22 16:35:01 +00:00
			`RSpec.describe Group, type: :model do`
Prevent namespace collisions for let/subject in shared examples When referencing shared example groups in specs, use it_behaves_like instead of include_examples. This runs shared examples in their own, nested context, so that any top-level let/subject methods in the spec do not leak into the shared example groups. 2019-01-24 10:13:04 +00:00			`it_behaves_like 'ApplicationModel'`
Refactoring: Eliminate explicit coupling of classes in ChecksImport concern 2019-01-28 06:04:05 +00:00			`it_behaves_like 'CanBeImported'`
Fixed issues #1259 and #1598 by adding ObjectManager::Attribute validations. 2019-03-13 23:51:22 +00:00			`it_behaves_like 'HasObjectManagerAttributesValidation'`
Refactoring: Migrate ApplicationModel::ChecksImport part of db_auto_increment_test.rb to RSpec 2019-01-22 16:35:01 +00:00			`end`