I ran into an error when running box validations where a non-zero exit code was produced. I received a stack trace on the SSH command step (And I run "mount|grep veewee-validation" over ssh).
I would expect the runtime exception not to have been raised and the subsequent validation step (I should see veewee-validation) to catch the error (which provides more descriptive and valuable insight into the actual issue).
Ideally the cucumber code should do any needed validation (check output,exit codes, etc), thus runtime exceptions should not be thrown in the event of a bad exit code during tests.
added option to not check exit code on SSH commands during box valida…
minor change to change redundant Error output (it was printing the er…
…ror message twice) to output the messege then the stack trace