Sha256: 0629b1f0107ded82c4b60805436846bc42b3beee3c289bb9e14ccace2c1d50ed
Contents?: true
Size: 1.88 KB
Versions: 12
Compression:
Stored size: 1.88 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 Vagrant support
When I run the cookbook command to create "sparkle_motion" with options:
| --vagrant |
Then I should have a new cookbook skeleton "sparkle_motion" with Vagrant support
And the exit status should be 0
Scenario: creating a new cookbook skeleton with Git support
When I run the cookbook command to create "sparkle_motion" with options:
| --git |
Then I should have a new cookbook skeleton "sparkle_motion" with Git support
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
Version data entries
12 entries across 12 versions & 1 rubygems