summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThe Bundler Bot <bot@bundler.io>2018-03-07 20:38:10 +0000
committerThe Bundler Bot <bot@bundler.io>2018-03-07 20:38:10 +0000
commitc9fa5359c9b320d0c96d062d19f730e912a6277a (patch)
tree36bc7da682d8bb2b4c5a811ded0c390b5c3c1d40
parentffe58a33ecf36997d071b980e87239ccf5365421 (diff)
parentddcc4a713905042932c8cddd27a6e4c4fa029a98 (diff)
downloadbundler-c9fa5359c9b320d0c96d062d19f730e912a6277a.tar.gz
Auto merge of #6328 - bundler:seg-spec-lock-no-download, r=colby-swandale
Add a spec for bundle lock not downloading gems ### What was the end-user problem that led to this PR? The problem was we were unsure (in https://github.com/bundler/bundler/issues/6312) whether lock had this behavior. ### What was your diagnosis of the problem? My diagnosis was it did, and I came to that conclusion via this test!
-rw-r--r--spec/commands/lock_spec.rb13
1 files changed, 13 insertions, 0 deletions
diff --git a/spec/commands/lock_spec.rb b/spec/commands/lock_spec.rb
index b08cc865b1..bd5bdfff2f 100644
--- a/spec/commands/lock_spec.rb
+++ b/spec/commands/lock_spec.rb
@@ -114,6 +114,19 @@ RSpec.describe "bundle lock" do
expect(read_lockfile).to eq(@lockfile)
end
+ it "can lock without downloading gems" do
+ gemfile <<-G
+ source "file://#{gem_repo1}"
+
+ gem "thin"
+ gem "rack_middleware", :group => "test"
+ G
+ bundle! "config set without test"
+ bundle! "config set path .bundle"
+ bundle! "lock"
+ expect(bundled_app(".bundle")).not_to exist
+ end
+
# see update_spec for more coverage on same options. logic is shared so it's not necessary
# to repeat coverage here.
context "conservative updates" do