Sha256: bab33839dce8b54213008a800341c5d33342bf14ed265d2e7f474b777e1abf7b

Contents?: true

Size: 1.9 KB

Versions: 3

Compression:

Stored size: 1.9 KB

Contents

Feature: cookbook command
  As a Cookbook author  
  I want a way to quickly generate a Cookbook skeleton that contains supporting Berkshelf files
  So I can quickly and automatically generate a Cookbook containing Berkshelf supporting files or other common supporting files

  Scenario: creating a new cookbook skeleton
    When I run the cookbook command to create "sparkle_motion"
    Then I should have a new cookbook skeleton "sparkle_motion"
    And the exit status should be 0

  Scenario: creating a new cookbook skeleton with Foodcritic support
    When I run the cookbook command to create "sparkle_motion" with options:
      | --foodcritic |
    Then I should have a new cookbook skeleton "sparkle_motion" with Foodcritic support
    And the exit status should be 0

  Scenario: creating a new cookbook skeleton with SCMVersion support
    When I run the cookbook command to create "sparkle_motion" with options:
      | --scmversion |
    Then I should have a new cookbook skeleton "sparkle_motion" with SCMVersion support
    And the exit status should be 0

  Scenario: creating a new cookbook skeleton without Bundler support
    When I run the cookbook command to create "sparkle_motion" with options:
      | --no-bundler |
    Then I should have a new cookbook skeleton "sparkle_motion" without Bundler support
    And the exit status should be 0

  Scenario: creating a new cookbook skeleton without Git support
    When I run the cookbook command to create "sparkle_motion" with options:
      | --skip-git |
    Then I should have a new cookbook skeleton "sparkle_motion" without Git support
    And the exit status should be 0

  Scenario: creating a new cookbook skeleton without Vagrant support
    When I run the cookbook command to create "sparkle_motion" with options:
      | --skip-vagrant |
    Then I should have a new cookbook skeleton "sparkle_motion" without Vagrant support
    And the exit status should be 0

Version data entries

3 entries across 3 versions & 1 rubygems

Version Path
berkshelf-1.0.0.rc1 features/cookbook_command.feature
berkshelf-0.6.0.beta4 features/cookbook_command.feature
berkshelf-0.6.0.beta3 features/cookbook_command.feature