Contents

Feature: berks verify
  Scenario: running verify when there is no Lockfile present
    Given a cookbook named "sparkle_motion"
    And I cd to "sparkle_motion"
    And I have a Berksfile pointing at the local Berkshelf API with:
      """
      metadata
      """
    And I run `berks verify`
    Then the output should contain:
      """
      Lockfile not found! Run `berks install` to create the lockfile.
      """
    And the exit status should be "LockfileNotFound"

  Scenario: running verify when there is a valid Lockfile present
    Given a cookbook named "sparkle_motion"
    And I cd to "sparkle_motion"
    And I have a Berksfile pointing at the local Berkshelf API with:
      """
      metadata
      """
    When I successfully run `berks install`
    And I successfully run `berks verify`
    Then the output should contain:
      """
      Verifying (1) cookbook(s)...
      Verified.
      """

Version data entries

51 entries across 51 versions & 1 rubygems

Version	Path
berkshelf-7.0.7	features/commands/verify.feature
berkshelf-6.3.4	features/commands/verify.feature
berkshelf-7.0.6	features/commands/verify.feature
berkshelf-7.0.5	features/commands/verify.feature
berkshelf-6.3.3	features/commands/verify.feature
berkshelf-7.0.4	features/commands/verify.feature
berkshelf-7.0.3	features/commands/verify.feature
berkshelf-7.0.2	features/commands/verify.feature
berkshelf-7.0.1	features/commands/verify.feature
berkshelf-7.0.0	features/commands/verify.feature
berkshelf-6.3.2	features/commands/verify.feature
berkshelf-6.3.1	features/commands/verify.feature
berkshelf-6.3.0	features/commands/verify.feature
berkshelf-6.2.2	features/commands/verify.feature
berkshelf-6.2.1	features/commands/verify.feature
berkshelf-6.2.0	features/commands/verify.feature
berkshelf-6.1.1	features/commands/verify.feature
berkshelf-6.1.0	features/commands/verify.feature
berkshelf-6.0.1	features/commands/verify.feature
berkshelf-6.0.0	features/commands/verify.feature