rtyler
/
blimpy
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity

Fixing the unit test failure 

Since these tests do not use any livery, explicit wait_for_ssh command
is required
This commit is contained in:
Kohsuke Kawaguchi 2013-03-29 15:56:18 -07:00
parent 2edd265e92
commit 8827307296
3 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
features/cli/scp.feature
View File

@ -13,7 +13,8 @@ Feature: SCP a file into a named VM
end
"""
And I have a file named "hello.txt"
When I run `blimpy scp Gherkins hello.txt`
When I run `blimpy wait_for_ssh`
And I run `blimpy scp Gherkins hello.txt`
Then the exit status should be 1
And the output should contain:
"""
@ -34,5 +35,6 @@ Feature: SCP a file into a named VM
"""
And I have a file named "hello.txt"
And I run `blimpy start`
When I run `blimpy scp "Cucumber Host" hello.txt`
When I run `blimpy wait_for_ssh`
And I run `blimpy scp "Cucumber Host" hello.txt`
Then the exit status should be 0

3
features/cli/ssh.feature
View File

@ -12,7 +12,8 @@ Feature: SSH into a named VM
end
end
"""
When I run `blimpy ssh Gherkins`
When I run `blimpy wait_for_ssh`
And I run `blimpy ssh Gherkins`
Then the exit status should be 1
And the output should contain:
"""

1
features/step_definitions/cli_steps.rb
View File

@ -34,6 +34,7 @@ end
When /^I ssh into the machine$/ do
step %{I run `blimpy start`}
step %{I run `blimpy wait_for_ssh`}
step %{I run `blimpy ssh "Cucumber Host" -o StrictHostKeyChecking=no` interactively}
end