acceptance/command/status_spec.rb in vagrant-orchestrate-0.5.0 vs acceptance/command/status_spec.rb in vagrant-orchestrate-0.5.1

- old
+ new

@@ -11,11 +11,11 @@ environment.skeleton("basic") end it "handles no status file gracefully" do # Make sure we're starting from a clean slate, rspec order isn't guaranteed. - execute("vagrant", "ssh", "-c", "\"rm -rf /var/state/vagrant_orchestrate\" /managed-1/") + execute("vagrant", "ssh", "-c", "\"rm -rf /var/state/vagrant_orchestrate\" managed-1") # All commands are executed against a single machine to reduce variability result = execute("vagrant", "orchestrate", "status", "/managed-1/") expect(result.stdout).to include("Status unavailable.") end @@ -23,9 +23,10 @@ # Because vagrant-spec executes in a clean tmp folder, it isn't a git repo, # and the normal git commands don't work. We'll inject some test data using # environment variables. See vagrant-orchestrate/repo_status.rb for impl. ENV["VAGRANT_ORCHESTRATE_STATUS_TEST_REF"] = TEST_REF ENV["VAGRANT_ORCHESTRATE_STATUS_TEST_REMOTE_ORIGIN_URL"] = TEST_REMOTE_ORIGIN_URL + ENV["VAGRANT_ORCHESTRATE_NO_GUARD_CLEAN"] = "true" execute("vagrant", "orchestrate", "push", "/managed-1/") result = execute("vagrant", "orchestrate", "status", "/managed-1/") status = VagrantPlugins::Orchestrate::RepoStatus.new # Punting on date. Can always add it later if needed expect(result.stdout).to include(status.ref)