This is our first time extending FactoryBot::SyntaxRunner. Do you think this should be something people opt in to? Will this break anything?

I can't think of how this could break existing tests but maybe I'm just not being creative enough.

This should be added to the NEWS as well (under a unreleased header)

Hi @seanpdoyle - here's an anecdote for you in case it's useful elsewhere. Having the option to opt out of this turned out to be necessary (and worked).

My tests already included fixture support, which I had mixed into FactoryBot in a different way here.

After updating to 6.5.0, my Rspec tests continued to pass but my integration tests (written in Spinach) all started to fail with the same error:

file_fixture delegated to self.class.file_fixture_support, but self.class.file_fixture_support is nil
        /home/runner/work/name.pn/name.pn/vendor/bundle/ruby/3.4.0/gems/factory_bot_rails-6.5.0/lib/factory_bot_rails/file_fixture_support.rb:6:in 'FactoryBot::SyntaxRunner#file_fixture'

I think this is because the Railtie assumes the testing system is Rspec, and if it's something other than Rspec, it leaves self.class.file_fixture_support as nil. It might be worth having some documentation about how to add this support into non-Rspec testing environments, since I'd prefer to use your upstream support rather than my home-rolled one, but I couldn't quite figure out how it works.

I ran into a problem with this because I use FactoryBot for $ rails db:seed.

This was my workaround:

# config/initializers/factory_bot.rb
return unless defined?(FactoryBot)

require 'active_support/testing/file_fixtures'
module RailsFileFixturesAnywhere
  extend ActiveSupport::Testing::FileFixtures

  def self.fixture_file_upload(filename)
    Rack::Test::UploadedFile.new file_fixture(filename).to_s
  end

  def self.file_fixture_path
    Rails.root.join("spec/fixtures/files")
  end
end

FactoryBot::SyntaxRunner.include FactoryBotRails::FileFixtureSupport
FactoryBot::SyntaxRunner.file_fixture_support = RailsFileFixturesAnywhere