mirror of
https://github.com/capistrano/capistrano
synced 2023-03-27 23:21:18 -04:00
27a8fbe8ef
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.
21 lines
632 B
Gherkin
21 lines
632 B
Gherkin
Feature: Installation
|
|
|
|
Background:
|
|
Given a test app without any configuration
|
|
|
|
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
|
|
|
|
Scenario: With default stages
|
|
When I run "cap install"
|
|
Then the deploy.rb file is created
|
|
And the default stage files are created
|
|
And the tasks folder is created
|
|
|
|
Scenario: With specified stages
|
|
When I run "cap install STAGES=qa,production"
|
|
Then the deploy.rb file is created
|
|
And the specified stage files are created
|
|
And the tasks folder is created
|