allow users to use fixture_path and transactional_fixtures settings

[swaroopmurthy]

We have a project where we're using
config.fixture_path
config.use_transactional_fixtures

Why was this removed?

[cupakromer]

Was this meant to be added to rspec/rspec-rails? Those configuration options have not been removed. They are set in rspec/rails/configuration.rb.

[swaroopmurthy]

Apologies, we must be doing it in the wrong order. I'm getting this error:
uninitialized constant RSpec::Rails::ControllerExampleGroup

from the following sequence:
require 'rspec/rails/extensions/active_record/proxy'
require 'rspec/rails/adapters'
require 'rspec/rails/configuration'
require 'rspec/rails/fixture_support'

[cupakromer]

You should just be using require 'rspec/rails' after loading your Rails configuration. The default generated spec/rails_helper.rb starts with:

# This file is copied to spec/ when you run 'rails generate rspec:install'
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../../config/environment', __FILE__)
# Prevent database truncation if the environment is production
abort("The Rails environment is running in production mode!") if Rails.env.production?
require 'spec_helper'
require 'rspec/rails'

It is not intended to piecewise load rspec-rails.

[cupakromer]

Is this by any chance the issue reported in #1355 fixed in #1372?

[cupakromer]

@swaroopmurthy please let us know if you're still seeing this issue. If so please make sure you've updated to the lasted to get the prior mentioned fix. Cheers!