kotovalexarian-likes-github/capistrano
1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Code Releases Activity
capistrano/features/step_definitions/cap_commands.rb

12 lines
280 B
Ruby
Raw Normal View History

Integration tests with Vagrant and Cucumber This commit removes the existing 'local' integration tests and replaces them with Cucumber features running against VMs. At this stage, some of the assertions are pending due to the limited nature of the response returned when executing commands through Vagrant, but the framework is there as a starting point to build upon. To run the suite: bundle exec cucumber During development, avoid scraping the VM between runs: bundle exec cucumber KEEPING_RUNNING=1 Ultimately I would like to see the `TestApp` helpers along with the Vagrant integration packaged and available for use when developing gems that work with Cap. For now though, this closes #641
2013-09-27 06:45:55 -04:00
When(/^I run cap "(.*?)"$/) do |task|
Update assertions for 'git:check' test scenario Capistrano 'git:check' task executes a `git ls-remote -h #{repo_url}` command to check if remote repo is accessible. If successful, command output is a list of references and their SHAs. Task should be successful and we're pretty sure remote repo will have a `master` reference, so that's what we're asserting. We're NOT asserting: * repo references other than master - likely to change * reference SHAs - will definitely change
2014-04-25 16:03:22 -04:00
@success, @output = TestApp.cap(task)
Integration tests with Vagrant and Cucumber This commit removes the existing 'local' integration tests and replaces them with Cucumber features running against VMs. At this stage, some of the assertions are pending due to the limited nature of the response returned when executing commands through Vagrant, but the framework is there as a starting point to build upon. To run the suite: bundle exec cucumber During development, avoid scraping the VM between runs: bundle exec cucumber KEEPING_RUNNING=1 Ultimately I would like to see the `TestApp` helpers along with the Vagrant integration packaged and available for use when developing gems that work with Cap. For now though, this closes #641
2013-09-27 06:45:55 -04:00
end
When(/^I run cap "(.*?)" as part of a release$/) do |task|
TestApp.cap("deploy:new_release_path #{task}")
end
Allow configuration location to be configurable This change allows both the `deploy_config_path` and `stage_config_path` to be moved from the default locations of `config/deploy.rb` and `config/deploy` respectively. These values __must__ be set in the `Capfile` prior to `capistrano/setup` being called, for example: set :deploy_config_path, 'app/config/deploy.rb' set :stage_config_path, 'app/config/deploy' # Load DSL and Setup Up Stages require 'capistrano/setup' Fixes #610
2013-10-11 12:24:37 -04:00
When(/^I run "(.*?)"$/) do |command|
:panda_face: Updated the loading default config tasks and stages config tasks. To show all tasks decalred in default config and stages files was missed from the tasks list. Added default value for :stage and load all default configs. Also added cucumber tests.
2014-01-18 16:18:55 -05:00
@success, @output = TestApp.run(command)
Allow configuration location to be configurable This change allows both the `deploy_config_path` and `stage_config_path` to be moved from the default locations of `config/deploy.rb` and `config/deploy` respectively. These values __must__ be set in the `Capfile` prior to `capistrano/setup` being called, for example: set :deploy_config_path, 'app/config/deploy.rb' set :stage_config_path, 'app/config/deploy' # Load DSL and Setup Up Stages require 'capistrano/setup' Fixes #610
2013-10-11 12:24:37 -04:00
end
Copy permalink