1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Commit graph

7 commits

Author SHA1 Message Date
William Johnston
b53e550fc0 Fix Style/StringLiterals 2016-02-28 17:56:07 -06:00
Lee Hambley
6235d5cdc1 Remove rubysl from the rbx gem group 2014-11-17 10:55:08 +01:00
Rustam Zagirov
2c14957bf4 move to rspec 3 2014-08-12 22:52:37 +04:00
Matt Brictson
738f5909fe Tests fail with Rspec 3, so pin at 2.14.x. 2014-06-07 21:43:45 -07:00
Travis Petticrew
2e13a1319c Cucumber tests will now run on the latest Vagrant
This removes the dependency on the `kuroko` gem and uses the Vagrant
command line application to control the virtual environment. The
`vagrant` command should be in your path, but if it isn't the path can
be set with the `VAGRANT_BIN` environment variable. This may even work
on older versions of Vagrant, but they are untested.

The `VagrantHelpers` module was added to mimic some of the API that was
provided by `kuroko`. The `RemoteCommandHelpers` module was modified to
accommodate those changes. Any non-zero exit status on a remote command
will raise a `VagrantHelpers::VagrantSSHCommandError` and should be
expected by any tests using the command helpers. All existing tests
work as expected.

In addition, a couple of minor changes were made. The TestApp utilizes
the Pathname library but does not require it. This was causing the suite
to fail for me so I added an explicit require. Also, the test for the
existence of a release directory would give a false positive on
subsequent runs if the `KEEP_RUNNING` option was used. I added an
`at_exit` that removes the test deployment directory to clean up the
box for the next run.

Documentation was also added to the README for how to run the test
suites.
2014-04-23 10:19:20 -05:00
Michael Nikitochkin
8bba22579c 🐼 Fixed failed tests
After update to new version of sskit there were a lot of failed tests.
2014-01-09 01:47:05 +02:00
seenmyfate
3d88a6755a initial commit 2013-02-01 09:19:14 +00:00