repo_manager 0.7.1

data/features/actions/task.feature

@@ -0,0 +1,127 @@
+@announce
+Feature: Invoke external tasks, normally Thor tasks.
+
+  Tasks can be defined by the app and placed in lib/tasks or tasks can be
+  defined by the user and placed in the user tasks folder.
+
+  Examples
+
+      repo task test:init /to/some/folder
+
+  Task action is not required
+
+      repo test:init /to/some/folder
+
+  Add user tasks by specifying folders.tasks in the master config file
+  and add Thor tasks.  See background scenario.
+
+  Background: A master configuration file
+    Given a file named "repo.conf" with:
+      """
+      ---
+      options:
+        color       : true
+      folders:
+        assets           : repo_manager/assets
+        tasks            : repo_manager/tasks
+      """
+    And an empty file named "output/.gitignore"
+    And a file named "repo_manager/tasks/test.rb" with:
+      """
+      module RepoManager
+        class Test < Thor
+          namespace :test
+
+          desc "init", "a test init task"
+          def init(path)
+            say path
+            return 0
+          end
+
+        end
+      end
+      """
+    And a file named "repo_manager/tasks/test.thor" with:
+      """
+      module RepoManager
+        class TestB < Thor
+
+          desc "hello", "a test hello task"
+          def hello(message)
+            say message
+            return 0
+          end
+
+        end
+      end
+      """
+
+  Scenario: Listings available tasks from gem and user task locations
+    When I run `repo task -T --verbose`
+    Then the exit status should be 0
+    And the output should not contain:
+      """
+      thor generate:configs FOLDER
+      """
+    And the output should contain:
+      """
+      repo test:init
+      """
+    And the output should contain:
+      """
+      repo repo_manager:test_b:hello
+      """
+
+  Scenario: Listings available tasks without the 'task' action
+    When I run `repo -T`
+    Then the exit status should be 0
+    And the output should contain:
+      """
+      repo test:init
+      """
+
+  Scenario: Show help for a given task
+    When I run `repo task help test:init`
+    Then the exit status should be 0
+    Then the output should contain:
+      """
+      Usage:
+        repo test:init
+
+      a test init task
+      """
+
+  Scenario: Show help for a given task without the 'task' action
+    When I run `repo help test:init`
+    Then the exit status should be 0
+    Then the output should contain:
+      """
+      Usage:
+        repo test:init
+
+      a test init task
+      """
+
+  Scenario: Successful task run without the 'repo_manager:' namespace
+    When I run `repo task test:init my_path`
+    Then the exit status should be 0
+    Then the output should contain:
+      """
+      my_path
+      """
+
+  Scenario: Successful task run without the 'task' action
+    When I run `repo test:init my_path`
+    Then the exit status should be 0
+    Then the output should contain:
+      """
+      my_path
+      """
+
+  Scenario: Successful task run with the 'repo_manager:' namespace
+    When I run `repo task repo_manager:test_b:hello my_message`
+    Then the exit status should be 0
+    Then the output should contain:
+      """
+      my_message
+      """

data/features/assets/configuration.feature

@@ -0,0 +1,204 @@
+@announce
+Feature: Asset configuration
+
+  The application should process and manage asset configuration via YAML.
+
+  A list of assets can be found by globbing '*/' in the data folder to return a
+  list of folder names.
+
+  For each asset in the data folder, initialize an array of assets by passing
+  in the user asset config filename and a hash of options
+
+  Example general settings repo.conf
+
+      ---
+      options:
+        color  : true
+      user:
+        my_str : "user defined string"
+        my_int : 12345
+      folders:
+        assets : data
+
+  Example with parent: config/data/assets/asset1/asset.conf:
+
+      ---
+      parent    : ../../global/assets/asset1
+      acquired  : 01/01/2011
+      launched  : 01/01/2011
+
+  Example without parent: config/data/assets/asset1/asset.conf:
+
+      ---
+      acquired  : 01/01/2011
+      launched  : 01/01/2011
+
+  Scenario: Specify assets folder explicity
+    Given a file named "repo.conf" with:
+      """
+      ---
+      folders:
+        assets      : data/app_assets
+      """
+    And a file named "data/app_assets/asset1/asset.conf" with:
+      """
+      ---
+      path: user_path
+      """
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    Then the output should contain:
+      """
+      path: user_path
+      """
+
+  Scenario: Specify assets folder explicity using a subfolder for the config file
+    Given a file named "repo_manager/repo.conf" with:
+      """
+      ---
+      folders:
+        assets      : data/app_assets
+      """
+    And a file named "repo_manager/data/app_assets/asset1/asset.conf" with:
+      """
+      ---
+      path: user_path
+      """
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    Then the output should contain:
+      """
+      path: user_path
+      """
+
+  Scenario: Assets folder determined by convention, relative to config file, by convention the folder name is 'assets'
+    Given a file named "repo.conf" with:
+      """
+      ---
+      options:
+        color       : AUTO
+      """
+    And a file named "assets/asset1/asset.conf" with:
+      """
+      ---
+      path: user_path
+      """
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    Then the output should contain:
+      """
+      path: user_path
+      """
+
+  Scenario: Config file is located in a subfolder
+    Given a file named "repo_manager/repo.conf" with:
+      """
+      ---
+      options:
+        color       : AUTO
+      """
+    And a file named "repo_manager/assets/asset1/asset.conf" with:
+      """
+      ---
+      path: user_path
+      """
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    Then the output should contain:
+      """
+      path: user_path
+      """
+
+  Scenario: Parent configuration fills in missing items with ERB evaluation
+    Given a file named "repo.conf" with:
+      """
+      ---
+      folders:
+        assets      : data/app_assets
+      """
+    And the folder "global/app_assets" with the following asset configurations:
+      | name         | path          | icon                      |
+      | default      | set_by_parent | based_on_<%= name %>.png  |
+    And the folder "data/app_assets" with the following asset configurations:
+      | name         | parent                           | binary          |
+      | asset1       | ../../global/app_assets/default  | path_to/bin.exe |
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    And the output should contain:
+      """
+      path: set_by_parent
+      """
+    And the output should contain:
+      """
+      icon: based_on_asset1.png
+      """
+
+  Scenario: User configuration file overrides global configuration file
+    Given a file named "repo.conf" with:
+      """
+      ---
+      folders:
+        assets      : data/app_assets
+      """
+    And the folder "global/app_assets" with the following asset configurations:
+      | name         | path          |
+      | default      | set_by_parent |
+    And the folder "data/app_assets" with the following asset configurations:
+      | name         | path          | parent                           | binary          |
+      | asset1       | set_by_user   | ../../global/app_assets/default  | path_to/bin.exe |
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    And the output should contain:
+      """
+      path: set_by_user
+      """
+    And the output should not contain:
+      """
+      path: set_by_parent
+      """
+
+  Scenario: Parent configuration missing
+    Given a file named "repo.conf" with:
+      """
+      ---
+      folders:
+        assets      : data/app_assets
+      """
+    And the folder "data/app_assets" with the following asset configurations:
+      | name         | parent                           | path            |
+      | asset1       | ../../global/app_assets/default  | path_to/bin.exe |
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    And the output should contain:
+      """
+      path: path_to/bin.exe
+      """
+
+  Scenario: Parent configuration blank
+    Given a file named "repo.conf" with:
+      """
+      ---
+      folders:
+        assets  : assets
+      """
+    And the folder "assets" with the following asset configurations:
+      | name         | parent             | path            |
+      | asset1       | ../global/default  | path_to/bin.exe |
+    And a file named "global/default/asset.conf" with:
+      """
+      ---
+      """
+    When I run `repo list --verbose --type=app_asset`
+    Then the exit status should be 0
+    And its output should not match /^WARN/
+    And its output should contain:
+      """
+      path: path_to/bin.exe
+      """

data/features/assets/rendering.feature

@@ -0,0 +1,42 @@
+@announce
+Feature: Asset template rendering
+
+  Assets should render Mustache variables.  When listing to STDOUT without a
+  template, the raw attribute will be shown.
+
+ Background: Empty configuration file so that we don't read global config locations
+   Given an empty file named "repo.conf"
+
+  Scenario: Render templates to STDOUT
+    Given a file named "test.erb" with:
+      """
+      <% require 'repo_manager/actions/action_helper' -%>
+      <% extend RepoManager::ActionHelper -%>
+
+      <% for item in items do -%>
+      <%= item.name %>:
+      ---
+      path: <%= relative_path(item.path) %>
+      <% end -%>
+      """
+    And a file named "assets/asset1/asset.conf" with:
+      """
+      ---
+      path: folder/{{name}}/another_folder
+      """
+    When I run `repo list --type=app_asset`
+    Then the exit status should be 0
+    And its output should contain:
+      """
+      path: folder/{{name}}/another_folder
+      """
+    When I run `repo list --template=test.erb --type=app_asset`
+    Then the exit status should be 0
+    And its output should not contain:
+      """
+      path: folder/{{name}}/another_folder
+      """
+    And its output should contain:
+      """
+      path: ./folder/asset1/another_folder
+      """

data/features/assets/user_attributes.feature

@@ -0,0 +1,98 @@
+@announce
+Feature: Create user defined attributes
+
+  The user can create an array of attribute names that will
+  be converted into read/write accessors at instantiation. This
+  allows using user defined attributes via Mustache tags in user
+  defined tasks.
+
+  Example defining user attributes
+
+      ---
+      user_attributes:
+      - my_folder
+      my_folder: folder name
+      path: folder/{{my_folder}}/another_folder
+
+  For simple variable replacement, there is no need to predefine the
+  Mustache tags variables.
+
+  Example ad hoc user attributes
+
+      ---
+      my_folder: folder name
+      path: folder/{{my_folder}}/another_folder
+
+  Background: Master config file and ERB template
+    Given a file named "repo.conf" with:
+      """
+      ---
+      folders:
+        assets      : assets
+      """
+    And a file named "test.erb" with:
+      """
+      <% require 'repo_manager/actions/action_helper' -%>
+      <% extend RepoManager::ActionHelper -%>
+
+      <% for item in items do -%>
+      <%= item.name %>:
+      ---
+      path: <%= relative_path(item.path) %>
+      <% end -%>
+      """
+
+  Scenario: Using user attributes with pre-defined read/write accessors
+    Given a file named "global/assets/default/asset.conf" with:
+      """
+      ---
+      user_attributes:
+      - my_folder
+      """
+    And a file named "assets/asset1/asset.conf" with:
+      """
+      ---
+      parent: ../global/assets/default
+      my_folder: folder name
+      path: folder/{{my_folder}}/another_folder
+      """
+    When I run `repo list --type=app_asset --verbose`
+    Then the exit status should be 0
+    And its output should contain:
+      """
+      path: folder/{{my_folder}}/another_folder
+      """
+    When I run `repo list --template=test.erb --type=app_asset --verbose`
+    Then the exit status should be 0
+    And its output should not contain:
+      """
+      path: folder/{{my_folder}}/another_folder
+      """
+    And its output should contain:
+      """
+      path: ./folder/folder name/another_folder
+      """
+
+  Scenario: Using user attributes with ad hoc template variable expansion
+    Given a file named "assets/asset1/asset.conf" with:
+      """
+      ---
+      my_folder: folder name
+      path: folder/{{my_folder}}/another_folder
+      """
+    When I run `repo list --type=app_asset --verbose`
+    Then the exit status should be 0
+    And its output should contain:
+      """
+      path: folder/{{my_folder}}/another_folder
+      """
+    When I run `repo list --template=test.erb --type=app_asset --verbose`
+    Then the exit status should be 0
+    And its output should not contain:
+      """
+      path: folder/{{my_folder}}/another_folder
+      """
+    And its output should contain:
+      """
+      path: ./folder/folder name/another_folder
+      """