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/installation.feature

22 lines
632 B
Gherkin
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
Feature: Installation
Background:
Use empty app as background for cap install tests Previously, a fully-configured app was used as the background for the `cap install` feature tests. This somewhat defeated the purpose of these tests, because `cap install` is supposed to be run on a project that hasn't yet been "capified".
2017-03-19 22:58:09 -04:00
Given a test app without any configuration
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
Allow `cap -T` to work when no Capfile is present Previously, the `cap -T` command assumed the presence of the `load:defaults` task. This task is only present if a proper Capfile is loaded, and so `cap -T` wouldn't work in a new, not yet "capified" project. This commit fixes the bug by testing that `load:defaults` is defined before calling it.
2017-03-19 23:02:38 -04:00
Scenario: The "install" task documentation can be viewed
When I run "cap -T"
Then the task is successful
And contains "cap install" in the output
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
Scenario: With default stages
Use empty app as background for cap install tests Previously, a fully-configured app was used as the background for the `cap install` feature tests. This somewhat defeated the purpose of these tests, because `cap install` is supposed to be run on a project that hasn't yet been "capified".
2017-03-19 22:58:09 -04:00
When I run "cap install"
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
Then the deploy.rb file is created
And the default stage files are created
And the tasks folder is created
Scenario: With specified stages
Use empty app as background for cap install tests Previously, a fully-configured app was used as the background for the `cap install` feature tests. This somewhat defeated the purpose of these tests, because `cap install` is supposed to be run on a project that hasn't yet been "capified".
2017-03-19 22:58:09 -04:00
When I run "cap install STAGES=qa,production"
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
Then the deploy.rb file is created
And the specified stage files are created
And the tasks folder is created
Copy permalink