Sha256: 50308de81a6e354095681f4cbdaf8def70c014bacfb4bc053638cb55240fdd0a

Contents?: true

Size: 1.54 KB

Versions: 2

Compression:

Stored size: 1.54 KB

Contents

Feature: berks contingent
  Background:
    * the Berkshelf API server's cache is empty
    * the Chef Server is empty
    * the cookbook store is empty


  Scenario: When there are dependent cookbooks
    Given the cookbook store has the cookbooks:
      | dep | 1.0.0 |
    And the cookbook store contains a cookbook "fake" "1.0.0" with dependencies:
      | dep | ~> 1.0.0 |
    And the cookbook store contains a cookbook "ekaf" "1.0.0" with dependencies:
      | dep | ~> 1.0.0 |
    And I have a Berksfile pointing at the local Berkshelf API with:
      """
      cookbook 'fake', '1.0.0'
      cookbook 'ekaf', '1.0.0'
      """
    And I successfully run `berks contingent dep`
    Then the output should contain:
      """
      Cookbooks in this Berksfile contingent upon dep:
        * ekaf (1.0.0)
        * fake (1.0.0)
      """


  Scenario: When there are no dependent cookbooks
    Given the cookbook store has the cookbooks:
      | fake | 1.0.0 |
    And I have a Berksfile pointing at the local Berkshelf API with:
      """
      cookbook 'fake', '1.0.0'
      """
    And I successfully run `berks contingent dep`
    Then the output should contain:
      """
      There are no cookbooks contingent upon 'dep' defined in this Berksfile
      """


  Scenario: When the cookbook is not in the Berksfile
    Given I have a Berksfile pointing at the local Berkshelf API
    And I successfully run `berks contingent dep`
    Then the output should contain:
      """
      There are no cookbooks contingent upon 'dep' defined in this Berksfile
      """

Version data entries

2 entries across 2 versions & 1 rubygems

Version Path
berkshelf-3.0.0.beta4 features/commands/contingent.feature
berkshelf-3.0.0.beta3 features/commands/contingent.feature