Contents

Feature: Deployment
  In order to get auto-tagging goodness
  As a ruby and git ninja
  I want cap to do all the work for me

  @0.1.5
  Scenario: user deploys with single file deploy.rb with 3 stages
    Given a three-stage app using single deploy file
    And a ci tag
    When I deploy to staging
    Then a tag should be added to git

  @0.1.5
  Scenario: user deploys with single file deploy.rb with no stages
    Given a one-stage app using single deploy file with the following environments:
      |production  |
    When I deploy
    Then a "production" tag should be added to git
    But I should not see "no branch available"

  @0.1.5
  Scenario: user deploys with single file deploy.rb stages with dashes in the name
    Given a one-stage app using single deploy file with the following environments:
      |staging            |
      |secret-production  |
    When I deploy to secret-production
    Then a "secret-production" tag should be added to git

  @0.1.5
  Scenario: user deploys with cap-ext multistage
    Given a three-stage app using cap-multistage
    And a ci tag
    When I deploy to staging
    Then a tag should be added to git

  @0.1.5
  Scenario: user sees latest tags
    Given a three-stage app using cap-multistage
    And a ci tag
    When I deploy to staging
    Then I should see "release tag history is:"

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
auto_tagger-0.2.4	features/deployment.feature
auto_tagger-0.2.3	features/deployment.feature
auto_tagger-0.2.2	features/deployment.feature
auto_tagger-0.2.1	features/deployment.feature