Sha256: 62b88fbdb4032ae2f94d538fe0809291d88d0b4baba39a2d57fdc498e4b2b40b
Contents?: true
Size: 1.38 KB
Versions: 15
Compression:
Stored size: 1.38 KB
Contents
Feature: Community
Background:
* I have a cookbook named "bacon"
Scenario: When the username does not exist
* the Stove config at "username" is unset
* I run `stove --no-git`
* it should fail with "requires a username"
Scenario: When the key does not exist
* the Stove config at "key" is unset
* I run `stove --no-git`
* it should fail with "requires a private key"
Scenario: With the default parameters
* the community server has the cookbook:
| bacon | 1.2.3 |
* I successfully run `stove --no-git`
* the community server will have the cookbooks:
| bacon | 0.0.0 |
Scenario: Yanking a cookbook
* the community server has the cookbooks:
| bacon | 1.2.3 |
* I successfully run `stove yank -l debug`
* the community server will not have the cookbooks:
| bacon | 1.2.3 |
* the output should contain "Successfully yanked bacon!"
Scenario: Yanking a cookbook by name
* the community server has the cookbooks:
| eggs | 4.5.6 |
* I successfully run `stove yank eggs`
* the community server will not have the cookbooks:
| eggs | 4.5.6 |
* the output should not contain "Successfully yanked bacon!"
* the output should contain "Successfully yanked eggs!"
Scenario: Yanking a non-existent cookbook
* I run `stove yank ham`
* it should fail with "I could not find a cookbook named ham"
Version data entries
15 entries across 15 versions & 2 rubygems