mirror of
https://github.com/capistrano/capistrano
synced 2023-03-27 23:21:18 -04:00
30 lines
1.2 KiB
Gherkin
30 lines
1.2 KiB
Gherkin
Feature: The path to the configuration can be changed, removing the need to
|
|
follow Ruby/Rails conventions
|
|
|
|
Background:
|
|
Given a test app with the default configuration
|
|
And servers with the roles app and web
|
|
|
|
Scenario: Deploying with configuration in default location
|
|
When I run "cap test"
|
|
Then the task is successful
|
|
|
|
Scenario: Deploying with configuration in a custom location
|
|
But the configuration is in a custom location
|
|
When I run "cap test"
|
|
Then the task is successful
|
|
|
|
Scenario: Show install task with configuration in default location
|
|
When I run "cap -T"
|
|
Then the task is successful
|
|
And contains "install" in the output
|
|
|
|
# Feature disabled because this is not how it works, we don't load
|
|
# tasks from stage files, as we expect them to be defined in ./lib/tasks
|
|
# Scenario: Show install task with configuration in a custom location
|
|
# And config stage file has line "desc 'Special Task'"
|
|
# And config stage file has line "task :special_stage_task"
|
|
# But the configuration is in a custom location
|
|
# When I run "cap -T"
|
|
# Then the task is successful
|
|
# And contains "special_stage_task" in the output
|