File: configuration.feature

package info (click to toggle)
capistrano 3.19.2-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 804 kB
  • sloc: ruby: 5,351; makefile: 5
file content (28 lines) | stat: -rw-r--r-- 1,031 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
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

  Scenario: Hide 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 doesn't contain "special_stage_task" in the output