thoughtbot--factory_bot_rails/features/step_definitions/appraisal.rb

When(/^I run `([^"]+)` with a clean environment$/) do |command|
  step <<~STEP
    I successfully run `ruby -e 'system({"BUNDLE_GEMFILE" => nil, "DISABLE_SPRING" => "true"}, "#{command}")'`
  STEP
end

When(/^I run `([^"]+)` with Spring enabled$/) do |command|
  step <<~STEP
    I successfully run `ruby -e 'system({"BUNDLE_GEMFILE" => nil}, "#{command}")'`
  STEP
end
Run standardrb This commit applies the changes from running `standardrb --fix` 2020-06-05 15:40:36 -04:00			When(/^I run `([^"]+)` with a clean environment$/) do \|command\|
Fix remaining RuboCop TODOs 2018-09-28 22:34:23 -04:00			`step <<~STEP`
			I successfully run `ruby -e 'system({"BUNDLE_GEMFILE" => nil, "DISABLE_SPRING" => "true"}, "#{command}")'`
			`STEP`
Improve the way we switch between project Gemfile and appraisal gemfiles Previously, the railties required by the project gemspec was in conflict with the rails versions being pulled in by Appraisal. There were situations where a newer rails app was generated by `rails new...` even though the Appraisal gemfiles/ value should have been setting it correctly. We need to be able to use the versions of things specified in the appraisal gemfiles/ specify the version of rails for the initial generation of the applications, but subsequently allow those applications to point to the `Gemfile` within the newly generated rails apps, rather than wherever BUNDLE_GEMFILE was previously set by Appraisal. 2012-12-19 14:46:21 -05:00			`end`
Write a failing test for reloading with Spring (#330) * Write a failing test for reloading with Spring This test captures what I think is going on in https://github.com/thoughtbot/factory_bot_rails/issues/323 Currently the factory_bot_rails reloader only reloads factory definitions when the definition files have changes (using `execute_if_updated`). This can cause problems when editing an application file without also editing a factory_bot definition file. Rails will reload the entire application, but will not reload the definitions. This causes factory_bot to have references to classes that were unloaded from the Rails application and replaced with new classes. https://github.com/thoughtbot/factory_bot_rails/pull/329 replaces `execute_if_updated` with `execute` so that factory_bot_rails will reload the definition files whenever anything in the application is changed. Hopefully that PR will get this test to pass! 2019-04-05 13:32:17 -04:00
Run standardrb This commit applies the changes from running `standardrb --fix` 2020-06-05 15:40:36 -04:00			When(/^I run `([^"]+)` with Spring enabled$/) do \|command\|
Write a failing test for reloading with Spring (#330) * Write a failing test for reloading with Spring This test captures what I think is going on in https://github.com/thoughtbot/factory_bot_rails/issues/323 Currently the factory_bot_rails reloader only reloads factory definitions when the definition files have changes (using `execute_if_updated`). This can cause problems when editing an application file without also editing a factory_bot definition file. Rails will reload the entire application, but will not reload the definitions. This causes factory_bot to have references to classes that were unloaded from the Rails application and replaced with new classes. https://github.com/thoughtbot/factory_bot_rails/pull/329 replaces `execute_if_updated` with `execute` so that factory_bot_rails will reload the definition files whenever anything in the application is changed. Hopefully that PR will get this test to pass! 2019-04-05 13:32:17 -04:00			`step <<~STEP`
			I successfully run `ruby -e 'system({"BUNDLE_GEMFILE" => nil}, "#{command}")'`
			`STEP`
			`end`