diff options
| author | Robert Speicher <rspeicher@gmail.com> | 2017-07-10 20:18:03 +0300 |
|---|---|---|
| committer | Robert Speicher <rspeicher@gmail.com> | 2017-07-10 20:18:03 +0300 |
| commit | 4144352aae9a13b6efe1424aa4f7422b30163201 (patch) | |
| tree | b4634c4ea8ab015d3d2d6258330ad0d99edad244 /spec/support | |
| parent | 03b0fe6df908db9d9d71f9f1a8e1e492d2719524 (diff) | |
Don't attempt to warm the Capybara cache outside of CI
We initially started doing this because the first feature test to use
the JavaScript driver would often time out due to asset compilation on
CI. We should still do it in CI since the cost is (relatively) low, but
doing so for every local run is both tiresome and generally unnecessary,
as developer machines will be faster than most shared CI runners, and
the cost of retrying a test after a timeout is much, much lower.
Diffstat (limited to 'spec/support')
| -rw-r--r-- | spec/support/test_env.rb | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/spec/support/test_env.rb b/spec/support/test_env.rb index 0cae5620920..0a194ca4c90 100644 --- a/spec/support/test_env.rb +++ b/spec/support/test_env.rb @@ -206,6 +206,7 @@ module TestEnv # Otherwise they'd be created by the first test, often timing out and # causing a transient test failure def eager_load_driver_server + return unless ENV['CI'] return unless defined?(Capybara) puts "Starting the Capybara driver server..." |