repo_manager 0.7.1

data/features/bin.feature

@@ -0,0 +1,42 @@
+@announce
+Feature: Options via a command line interface (CLI)
+
+  The application should accept options on the command line.  These options
+  should override hard coded defaults
+
+ Background: Empty configuration file so that we don't read global config locations
+   Given an empty file named "repo.conf"
+
+  Scenario: Version info
+    When I run `repo --version`
+    Then the exit status should be 0
+    And the output should match /repo_manager, version ([\d]+\.[\d]+\.[\d]+$)/
+
+  Scenario: Help
+    When I run `repo --help`
+    Then the exit status should be 0
+    And the output should match:
+      """
+      .*
+        Usage: .*
+      """
+
+  Scenario: Invalid option
+    When I run `repo --non-existing-option`
+    Then the exit status should be 1
+    And the output should match:
+      """
+      ^.* invalid option: --non-existing-option
+      ^.* --help for more information
+
+      """
+
+  Scenario: Invalid action
+    When I run `repo non-existing-action`
+    Then the exit status should be 1
+    And the output should match:
+      """
+      ^.* invalid action: non-existing-action
+      ^.* --help for more information
+
+      """

data/features/logger.feature

@@ -0,0 +1,218 @@
+@announce
+Feature: Logging to console and log files
+
+  The application outputs warnings and error messages on the console by
+  default.  These same messages can be optionally logged to file.
+
+  Logging configuration is handled in the YAML config file.  There are no
+  command line modifiers.
+
+  Configuration Notes:
+
+  Log levels can be one of: debug, info, warn, error, or fatal
+
+  All logging configuration is under the key "logging".  Configuration
+  specified will overwrite the hard-coded defaults.
+
+  See the orginal test fixture here:
+  https://github.com/TwP/logging/blob/master/data/logging.yaml
+
+  Scenario: Debug output to console via the "--verbose" switch
+    Given a file named "repo.conf" with:
+      """
+      ---
+      """
+    When I run `repo help --verbose`
+    Then the output should contain:
+      """
+      DEBUG
+      """
+
+  Scenario: No debug output to console without the "--verbose" switch
+    Given a file named "repo.conf" with:
+      """
+      ---
+      """
+    When I run `repo help`
+    Then the output should not contain:
+      """
+      DEBUG
+      """
+
+  Scenario: No debug output to console using a config file that only specifies a
+    logger type of File
+    Given a file named "repo.conf" with:
+      """
+      ---
+      options:
+        color: true
+      logging:
+        loggers:
+          - name          : root
+            appenders:
+              - logfile
+        appenders:
+          - type          : File
+            name          : logfile
+            level         : debug
+            truncate      : true
+            filename      : 'temp.log'
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+      """
+    When I run `repo help`
+    Then the output should not contain:
+      """
+      DEBUG
+      """
+    And the file "temp.log" should contain:
+      """
+      DEBUG
+      """
+
+  Scenario: Overriding root level 'info' with '--verbose' to turn on 'debug' level
+    Given a file named "repo.conf" with:
+      """
+      ---
+      options:
+        color: true
+      logging:
+        loggers:
+          - name          : root
+            appenders:
+              - logfile
+        appenders:
+          - type          : File
+            name          : logfile
+            level         : info
+            truncate      : true
+            filename      : 'temp.log'
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+      """
+    When I run `repo help --verbose`
+    Then the output should not contain:
+      """
+      DEBUG
+      """
+    And the file "temp.log" should contain:
+      """
+      DEBUG
+      """
+
+
+  Scenario: Override default STDOUT appender level with a config file
+    Given a file named "repo.conf" with:
+      """
+      ---
+      logging:
+        loggers:
+          - name          : root
+            appenders:
+              - logfile
+              - stdout
+        appenders:
+          - type          : Stdout
+            name          : stdout
+            level         : debug
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+              color_scheme: default
+          - type          : File
+            name          : logfile
+            level         : info
+            truncate      : true
+            filename      : 'temp.log'
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+      """
+    When I run `repo help`
+    Then the output should contain:
+      """
+      DEBUG
+      """
+    And the file "temp.log" should not contain:
+      """
+      DEBUG
+      """
+
+  Scenario: Stdout can be set to a different level than logfile
+    Given a file named "repo.conf" with:
+      """
+      ---
+      logging:
+        loggers:
+          - name          : root
+            appenders:
+              - logfile
+              - stdout
+        appenders:
+          - type          : Stdout
+            name          : stdout
+            level         : info
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+              color_scheme: default
+          - type          : File
+            name          : logfile
+            level         : debug
+            truncate      : true
+            filename      : 'temp.log'
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+      """
+    When I run `repo help`
+    Then the output should not contain:
+      """
+      DEBUG
+      """
+    And the file "temp.log" should contain:
+      """
+      DEBUG
+      """
+
+  Scenario: Override default STDOUT appender level with a config file for debug output
+    Given a file named "repo.conf" with:
+      """
+      ---
+      logging:
+        loggers:
+          - name          : root
+            appenders:
+              - logfile
+              - stdout
+        appenders:
+          - type          : Stdout
+            name          : stdout
+            level         : info
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+              color_scheme: default
+          - type          : File
+            name          : logfile
+            level         : info
+            truncate      : true
+            filename      : 'temp.log'
+            layout:
+              type        : Pattern
+              pattern     : '[%d] %l %c : %m\n'
+      """
+    When I run `repo help --verbose`
+    Then the output should contain:
+      """
+      DEBUG
+      """
+    And the file "temp.log" should contain:
+      """
+      DEBUG
+      """
+
+  @wip
+  Scenario: Logging to file with the truncate option

data/features/settings.feature

@@ -0,0 +1,240 @@
+@announce
+Feature: Configuration via YAML
+
+  The application should process configuration options via YAML. These options
+  should override hard coded defaults but not command line options.
+
+  Config files are read from multiple locations in order of priority.  Once a
+  config file is found, all other config files are ignored.
+
+
+  Config file priority:
+
+      ./repo.conf
+      ./.repo.conf
+      ./repo_manager/repo.conf
+      ./.repo_manager/repo.conf
+      ~/.repo.conf
+      ~/repo.conf
+      ~/repo_manager/repo.conf
+      ~/.repo_manager/repo.conf
+
+  All command line options can be read from the config file from the "options:"
+  block. The "options" block is optional.
+
+  NOTE: All file system testing is done via the Aruba gem.  The home folder
+  config file is stubbed to prevent testing contamination in case it exists.
+
+
+  Scenario: Specified config file exists
+    Given an empty file named "config.conf"
+    When I run `repo list --verbose --config config.conf`
+    Then the output should contain:
+      """
+      config file: config.conf
+      """
+
+  Scenario: Specified config file option but not given on command line
+    When I run `repo list --verbose --config`
+    Then the exit status should be 1
+    And the output should contain:
+      """
+      missing argument: --config
+      """
+
+  Scenario: Specified config file not found
+    When I run `repo path --verbose --config=config.conf`
+    Then the exit status should be 1
+    And the output should contain:
+      """
+      config file not found
+      """
+
+ Scenario: Ignoring the config file with the "--no-config" option
+    Given a file named "repo.conf" with:
+      """
+      ---
+      options:
+        color: true
+      """
+    When I run `repo list --verbose`
+    Then its output should contain:
+      """
+      :color=>true
+      """
+    When I run `repo list --verbose --no-config`
+    Then its output should contain:
+      """
+      :color=>"AUTO"
+      """
+    And its output should not contain:
+      """
+      :color=>true
+      """
+
+ Scenario: Reading options from specified config file, ignoring the
+    default config file
+    Given a file named "repo.conf" with:
+      """
+      ---
+      options:
+        color: true
+      """
+    And a file named "no_color.conf" with:
+      """
+      ---
+      options:
+        color: false
+      """
+    When I run `repo list --verbose --config no_color.conf`
+    Then the output should contain:
+      """
+      :color=>false
+      """
+    And the output should not contain:
+      """
+      :color=>true
+      """
+
+  Scenario: Reading options from specified config file, ignoring the
+    default config file with override on command line
+    Given a file named "repo.conf" with:
+      """
+      ---
+     options:
+        color: true
+      """
+    And a file named "no_color.conf" with:
+      """
+      ---
+     options:
+        color: false
+      """
+    When I run `repo list --verbose --config no_color.conf --color`
+    Then the output should contain:
+      """
+      :color=>"AUTO"
+      """
+    And the output should not contain:
+      """
+      :color=>false
+      """
+    And the output should not contain:
+      """
+      :color=>true
+      """
+
+ Scenario: Reading options from config file with negative override on command line
+    And a file named "with_color.conf" with:
+      """
+      ---
+      options:
+        color: true
+      """
+    When I run `repo list --verbose --config with_color.conf --no-color`
+    Then the output should contain:
+      """
+      :color=>false
+      """
+
+ Scenario: Negative override on command line with alternative spelling '--no-coloring'
+    And a file named "with_color.conf" with:
+      """
+      ---
+      options:
+        color: true
+      """
+    When I run `repo list --verbose --config with_color.conf --no-coloring`
+    Then the output should contain:
+      """
+      :color=>false
+      """
+
+  Scenario: Reading text options from config file
+    Given a file named "with_always_color.conf" with:
+      """
+      ---
+      options:
+        color: ALWAYS
+      """
+    When I run `repo list --verbose --config with_always_color.conf`
+    Then the output should contain:
+      """
+      :color=>"ALWAYS"
+      """
+
+  Scenario: Processing ERB
+    Given a file named "erb.conf" with:
+      """
+      ---
+      options:
+        color: <%= "ALWAYS" %>
+      """
+    When I run `repo list --verbose --config erb.conf`
+    Then the output should contain:
+      """
+      :color=>"ALWAYS"
+      """
+
+  Scenario: Reading default valid config files ordered by priority
+    Given a file named "repo.conf" with:
+      """
+      ---
+      user_var: user1
+      """
+    And a file named ".repo.conf" with:
+      """
+      ---
+      user_var: user2
+      """
+    And a file named "repo_manager/repo.conf" with:
+      """
+      ---
+      user_var: user3
+      """
+    When I run `repo list list=NAME --verbose`
+    Then the output should contain:
+      """
+      :user_var=>"user1"
+      """
+    And the output should not contain:
+      """
+      :user_var=>"user2"
+      """
+    And the output should not contain:
+      """
+      :user_var=>"user3"
+      """
+
+  Scenario: Reading default config file '.repo.conf'
+    Given a file named ".repo.conf" with:
+      """
+      ---
+      user_var: user2
+      """
+    And a file named "repo_manager/repo.conf" with:
+      """
+      ---
+      user_var: user3
+      """
+    When I run `repo list list=NAME --verbose`
+    Then the output should contain:
+      """
+      :user_var=>"user2"
+      """
+    And the output should not contain:
+      """
+      :user_var=>"user3"
+      """
+
+  Scenario: Reading default config file 'repo_manager/repo.conf
+    Given a file named "repo_manager/repo.conf" with:
+      """
+      ---
+      user_var: user3
+      """
+    When I run `repo list list=NAME --verbose`
+    Then the output should contain:
+      """
+      :user_var=>"user3"
+      """