Sha256: 4b3ff21ffb9eb22c347c647b6f0ccb78ccf31aa23be3f74bcc4543f5d999b5f5

Contents?: true

Size: 959 Bytes

Versions: 12

Compression:

Stored size: 959 Bytes

Contents

Feature: Run `msync update` without a good context

  Scenario: Run `msync update` without any module
    Given a directory named "moduleroot"
    When I run `msync update --message "In a bad context"`
    Then the exit status should be 1
    And the stderr should contain:
      """
      No modules found
      """

  Scenario: Run `msync update` without the "moduleroot" directory
    Given a basic setup with a puppet module "puppet-test" from "fakenamespace"
    When I run `msync update --message "In a bad context"`
    Then the exit status should be 1
    And the stderr should contain "moduleroot"

  Scenario: Run `msync update` without commit message
    Given a basic setup with a puppet module "puppet-test" from "fakenamespace"
    And a directory named "moduleroot"
    When I run `msync update`
    Then the exit status should be 1
    And the stderr should contain:
      """
      No value provided for required option "--message"
      """

Version data entries

12 entries across 12 versions & 1 rubygems

Version Path
modulesync-3.2.0 features/update/bad_context.feature
modulesync-3.1.0 features/update/bad_context.feature
modulesync-2.7.0 features/update/bad_context.feature
modulesync-2.6.0 features/update/bad_context.feature
modulesync-2.5.0 features/update/bad_context.feature
modulesync-2.4.0 features/update/bad_context.feature
modulesync-2.3.1 features/update/bad_context.feature
modulesync-2.3.0 features/update/bad_context.feature
modulesync-2.2.0 features/update/bad_context.feature
modulesync-2.1.1 features/update/bad_context.feature
modulesync-2.1.0 features/update/bad_context.feature
modulesync-2.0.2 features/update/bad_context.feature