features/vagrant-exec.feature in vagrant-exec-0.2.0 vs features/vagrant-exec.feature in vagrant-exec-0.2.1

- old
+ new

@@ -14,18 +14,18 @@ Scenario: uses /vagrant as default folder Given I run `bundle exec vagrant up` When I run `bundle exec vagrant exec pwd` Then the exit status should be 0 - And the output should contain "Executing single command on remote machine: cd /vagrant && pwd" + And the output should contain "Executing single command on remote machine: source ~/.profile && cd /vagrant && pwd" Scenario: can use custom folder Given I set vagrant-exec folder to "/tmp" And I run `bundle exec vagrant up` When I run `bundle exec vagrant exec pwd` Then the exit status should be 0 - And the output should contain "Executing single command on remote machine: cd /tmp && pwd" + And the output should contain "Executing single command on remote machine: source ~/.profile && cd /tmp && pwd" Scenario: raises error if folder is improperly set Given I set vagrant-exec folder to true And I run `bundle exec vagrant up` Then the exit status should not be 0 @@ -40,17 +40,17 @@ Scenario: can use bundler Given I set vagrant-exec bundler to true And I run `bundle exec vagrant up` When I run `bundle exec vagrant exec pwd` Then the exit status should not be 0 - And the output should contain "Executing single command on remote machine: cd /vagrant && bundle exec pwd" + And the output should contain "Executing single command on remote machine: source ~/.profile && cd /vagrant && bundle exec pwd" Scenario: does not use bundler for bundle commands Given I set vagrant-exec bundler to true And I run `bundle exec vagrant up` When I run `bundle exec vagrant exec bundle install` - Then the output should contain "Executing single command on remote machine: cd /vagrant && bundle install" + Then the output should contain "Executing single command on remote machine: source ~/.profile && cd /vagrant && bundle install" Scenario: raises error if bundler is improperly set Given I set vagrant-exec bundler to "true" When I run `bundle exec vagrant up` Then the exit status should not be 0 @@ -62,11 +62,11 @@ | TEST1 | true | | TEST2 | false | And I run `bundle exec vagrant up` When I run `bundle exec vagrant exec pwd` Then the exit status should be 0 - And the output should contain "Executing single command on remote machine: cd /vagrant && export TEST1=true && export TEST2=false && pwd" + And the output should contain "Executing single command on remote machine: source ~/.profile && cd /vagrant && export TEST1=true && export TEST2=false && pwd" Scenario Outline: shows help correctly Given I run `bundle exec vagrant up` When I run `bundle exec vagrant exec <args>` Then the output should contain "Usage: vagrant exec [options] <command>" @@ -79,10 +79,10 @@ | --help pwd -h | Scenario Outline: passes command arguments correctly Given I run `bundle exec vagrant up` When I run `bundle exec vagrant exec <cmd>` - Then the output should contain "Executing single command on remote machine: cd /vagrant && <cmd>" + Then the output should contain "Executing single command on remote machine: source ~/.profile && cd /vagrant && <cmd>" Examples: | cmd | | cwd . | | cwd ~ | | cwd -h |