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

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

# system({'BUNDLE_GEMFILE' => nil}, "cd tmp/aruba/testapp && #{command} && cd -")
Instead of modifying the environment, run bundle install in a new process JRuby does not support setting/unsetting environment variables. Thus, we will launch an entirely new process without the parents env when we run `bundle install` inside the generated rails apps, forcing them to use their own Gemfile, instead of the BUNDLE_GEMFILE setting from the main gem codebase. 2012-12-21 11:08:37 -05:00			When /^I run `([^"]+)` with a clean environment$/ do \|command\|
Test against Rails 3.2, 4.0, 4.1 * Remove gemfiles from version control to match same testing style as Clearance and Suspenders. * MiniTest does not need to be manually included as it is automatically included by Rails by default. * Add spring for Rails 4.1. * Disable Spring to get specs to pass on Rails 4.1. * Add therubyrhino for JRuby. * Remove old references to Rails 3. * Fix JRuby test where output is "1 runs", not "1 tests". * Remove Rails 3.0 reference to "turn". 2014-05-26 23:39:51 -04:00			step %{I successfully run `ruby -e 'system({"BUNDLE_GEMFILE" => nil, "DISABLE_SPRING" => "true"}, "#{command}")'`}
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`
Instead of modifying the environment, run bundle install in a new process JRuby does not support setting/unsetting environment variables. Thus, we will launch an entirely new process without the parents env when we run `bundle install` inside the generated rails apps, forcing them to use their own Gemfile, instead of the BUNDLE_GEMFILE setting from the main gem codebase. 2012-12-21 11:08:37 -05:00
			`# system({'BUNDLE_GEMFILE' => nil}, "cd tmp/aruba/testapp && #{command} && cd -")`