Contents

Feature: CLI
  ModuleSync needs to have a robust command line interface

  Scenario: When passing no arguments to the msync command
    When I run `msync`
    And the output should match /Commands:/
    Then the exit status should be 1

  Scenario: When passing invalid arguments to the msync update command
    When I run `msync update`
    And the output should match /No value provided for required option/
    Then the exit status should be 1

  Scenario: When passing invalid arguments to the msync hook command
    When I run `msync hook`
    And the output should match /Commands:/
    Then the exit status should be 1

  Scenario: When running the help command
    When I run `msync help`
    And the output should match /Commands:/
    Then the exit status should be 0

  Scenario: When overriding a setting from the config file on the command line
    Given a puppet module "puppet-test" from "fakenamespace"
    And a file named "managed_modules.yml" with:
      """
      ---
        - puppet-test
      """
    And a file named "modulesync.yml" with:
      """
      ---
      namespace: default
      """
    And a git_base option appended to "modulesync.yml" for local tests
    And a directory named "moduleroot"
    When I run `msync update --noop --namespace fakenamespace --branch command-line-branch`
    Then the exit status should be 0
    And the output should contain:
      """
      Creating new branch command-line-branch
      """

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
modulesync-2.2.0	features/cli.feature
modulesync-2.1.1	features/cli.feature
modulesync-2.1.0	features/cli.feature