-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh steps dependency on ssh-forever #5
Comments
Ack. I think I'll be reverting to use Aruba's step.
It is true that the current gem on rubyforge/rubygems is not great. It does need to be released with passing spec and features files. |
The above syntax doesn't seem to work for me. It complains on the steps not found. I tried this: When I run `ssh me@myserver pwd` interactively Then the stdout from "ssh me@myserver pwd" should contain "home" The problem seems to be with the pseudo tty allocation, I tried -t for ssh but no avail. Maybe I indeed need to try the github version? |
I've just pushed what I have to master. I'm stumped on why the Before hook is not defined, i.e. why cucumber does not seem to be loading. To see the breakage run Essentially I had to move the Aruba code into cuken to get step defs that were more, IMO, extensive, intuitive and consistent. This seems to be working for me in my project, so am stumped why it is broken in cuken's spec run. I don't have time to continue looking at this right now. Perhaps your fresh eyes might see somthing I have missed - and yes, I do ack the code is in need of a cleanup ;) |
I think I found the missing require/include. |
Hi, I've had a go with cuken again. The current gem (not github) fails to setup some of the ssh-steps.
It for example
I'd love to use cuken for #veewee, but currently I'm still undecided given the ssh-forever dependency.
I see the value of running it just through the command cmd/cuken sweet,
but I think there room for the same implementation through net/ssh .
How would you feel about this? Do I make a new cuken/netssh include and create the same ssh steps?
Or I create a step called And I successfully sshrun or something similar.
thanks for feedback
The text was updated successfully, but these errors were encountered: