producer-core 0.5.8 → 0.5.9

data/features/cli/target.feature

@@ -1,15 +0,0 @@
-Feature: CLI target option
-
-  Background:
-    Given a recipe with:
-      """
-      target 'some_host.example'
-
-      task :some_task do
-        echo env.target
-      end
-      """
-
-  Scenario: override the recipe target
-    When I successfully execute the recipe with option -t other_host.example
-    Then the output must contain exactly "other_host.example\n"

data/features/cli/usage.feature

@@ -1,13 +0,0 @@
-Feature: CLI usage
-
-  @exec
-  Scenario: prints the usage when an argument is missing
-    When I run `producer`
-    Then the exit status must be 64
-    And the output must contain exactly the usage
-
-  @exec
-  Scenario: prints the usage when unknown option switch is given
-    When I run `producer --unknown-option`
-    Then the exit status must be 64
-    And the output must contain exactly the usage

data/features/cli/verbose.feature

@@ -1,48 +0,0 @@
-Feature: CLI verbose option
-
-  Background:
-    Given a recipe with:
-      """
-      task :task_ok do
-        condition { true }
-
-        echo 'some message'
-      end
-
-      task :task_ko do
-        condition { false }
-      end
-      """
-
-  Scenario: prints tasks name
-    When I successfully execute the recipe with option -v
-    Then the output must match /Task:.+`task_ok'/
-    And  the output must match /Task:.+`task_ko'/
-
-  Scenario: appends `applying' or `skipped' after tasks name
-    When I successfully execute the recipe with option -v
-    Then the output must match /task_ok.+applying...$/
-    And  the output must match /task_ko.+skipped$/
-
-  Scenario: prints actions info
-    When I successfully execute the recipe with option -v
-    Then the output must match /^ action: echo/
-
-  Scenario: prints actions arguments
-    When I successfully execute the recipe with option -v
-    Then the output must match /echo \["some message"\]/
-
-  Scenario: summarizes printed actions arguments
-    Given a recipe with:
-      """
-      task :some_task do
-        echo 'long message ' * 32
-      end
-      """
-    When I successfully execute the recipe with option -v
-    Then the output must match /action: .{,70}$/
-
-  Scenario: enables verbose mode from the environment
-    Given I set the environment variable "PRODUCER_VERBOSE"
-    When I successfully execute the recipe
-    Then the output must contain "Task"

data/features/condition/negated_test.feature

@@ -1,47 +0,0 @@
-Feature: negated test prefix (no_)
-
-  Scenario: prefixed test fails when non-prefixed test is successful
-    Given a recipe with:
-      """
-      test_macro :even? do |n|
-        n % 2 == 0
-      end
-
-      task :successful_test do
-        condition { even? 4 }
-
-        echo 'successful_test'
-      end
-
-      task :negated_test do
-        condition { no_even? 4 }
-
-        echo 'negated_test'
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "successful_test"
-    And the output must not contain "negated_test"
-
-  Scenario: prefixed test succeed when non-prefixed test is failing
-    Given a recipe with:
-      """
-      test_macro :even? do |n|
-        n % 2 == 0
-      end
-
-      task :failing_test do
-        condition { even? 5 }
-
-        echo 'failing_test'
-      end
-
-      task :negated_test do
-        condition { no_even? 5 }
-
-        echo 'negated_test'
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must not contain "failing_test"
-    And the output must contain "negated_test"

data/features/condition/target.feature

@@ -1,15 +0,0 @@
-Feature: `target' condition keyword
-
-  Scenario: returns the current target
-    Given a recipe with:
-      """
-      target 'some_host.example'
-
-      task :test_target do
-        condition { target == 'some_host.example' }
-
-        echo 'OK'
-      end
-      """
-    When I execute the recipe
-    Then the output must contain "OK"

data/features/recipe/compose_macro.feature

@@ -1,29 +0,0 @@
-Feature: `compose_macro' recipe keyword
-
-  Background:
-    Given a recipe named "composed_macro.rb" with:
-      """
-      macro :hello do |prefix, *args|
-        echo 'hello %s %s' % [prefix, args.join(', ')]
-      end
-
-      compose_macro :hello_composed, :hello, 'composed'
-      """
-
-  Scenario: declares a composed macro as recipe keyword
-    Given a recipe with:
-      """
-      source 'composed_macro'
-      hello_composed :foo, :bar
-      """
-    When I successfully execute the recipe
-    Then the output must contain "hello composed foo, bar"
-
-  Scenario: declares a composed macro as task keyword
-    Given a recipe with:
-      """
-      source 'composed_macro'
-      task(:some_task) { hello_composed :foo, :bar }
-      """
-    When I successfully execute the recipe
-    Then the output must contain "hello composed foo, bar"

data/features/recipe/errors.feature

@@ -1,9 +0,0 @@
-Feature: recipe errors
-
-  Scenario: reports when remote target is invalid
-    Given a recipe with:
-      """
-      task(:some_task) { sh 'true' }
-      """
-    When I execute the recipe
-    Then the output must match /\ARemoteInvalidError:\s+\w+/

data/features/recipe/macro.feature

@@ -1,50 +0,0 @@
-Feature: `macro' recipe keyword
-
-  Scenario: declares a new recipe keyword accepting task code
-    Given a recipe with:
-      """
-      macro :hello do
-        echo 'hello macro'
-      end
-
-      hello
-      """
-    When I successfully execute the recipe
-    Then the output must contain "hello macro"
-
-  Scenario: declares a new task keyword
-    Given a recipe with:
-      """
-      macro(:hello) { echo 'hello macro' }
-
-      task(:some_task) { hello }
-      """
-    When I successfully execute the recipe
-    Then the output must contain "hello macro"
-
-  Scenario: supports arguments
-    Given a recipe with:
-      """
-      macro :my_echo do |kind, message|
-        echo "#{kind}: #{message}"
-      end
-
-      my_echo 'my', 'hello'
-      """
-    When I successfully execute the recipe
-    Then the output must contain "my: hello"
-
-  Scenario: supports arguments in conditions
-    Given a recipe with:
-      """
-      macro :my_echo do |message|
-        condition { message =~ /foo/ }
-
-        echo message
-      end
-
-      %w[foo bar].each { |e| my_echo e }
-      """
-    When I successfully execute the recipe
-    Then the output must contain "foo"
-    And the output must not contain "bar"

data/features/recipe/registry.feature

@@ -1,82 +0,0 @@
-Feature: key/value registry
-
-  Scenario: `get' keyword in a task fetches a value registered with `set'
-    Given a recipe with:
-      """
-      set :some_key, 'some_value'
-
-      task :registry_testing do
-        echo get :some_key
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_value"
-
-  Scenario: `get' keyword fetches a value from the recipe
-    Given a recipe with:
-      """
-      set :some_key, 'some_value'
-      set :other_key, get(:some_key)
-
-      task :registry_testing do
-        echo get :other_key
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_value"
-
-  Scenario: `get' keyword fetches a value from a condition
-    Given a recipe with:
-      """
-      set :some_key, 'some_value'
-
-      task(:ok) { condition { get :some_key }; echo get :some_key }
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_value"
-
-  Scenario: `get' keyword should trigger an error when given invalid key
-    Given a recipe with:
-      """
-      task :some_task do
-        echo get :no_key
-        echo 'after_fail'
-      end
-      """
-    When I execute the recipe
-    Then the output must not contain "after_fail"
-    And the output must match /\A\w+Error:\s+:no_key/
-
-  Scenario: `get' keyword accepts a default value
-    Given a recipe with:
-      """
-      task :registry_testing do
-        echo get(:some_key, 'some_value')
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_value"
-
-  Scenario: `set' keyword sets a value from a task
-    Given a recipe with:
-      """
-      task :registry_testing do
-        set :some_key, 'some_value'
-        echo get :some_key
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_value"
-
-  Scenario: `set?' keyword tests wether given key is defined
-    Given a recipe with:
-      """
-      set :some_key, 'some_value'
-      task :registry_testing do
-        echo 'some_value_set' if set? :some_key
-        echo 'other_value' if set? :other_key
-      end
-      """
-    When I execute the recipe
-    Then the output must contain "some_value_set"
-    And the output must not contain "other_value"

data/features/recipe/source.feature

@@ -1,17 +0,0 @@
-Feature: `source' recipe keyword
-
-  Background:
-    Given a recipe with:
-      """
-      source 'sourced_recipe'
-      """
-
-  Scenario: requires a recipe file
-    Given a file named "sourced_recipe.rb" with:
-      """
-      task :some_task do
-        echo 'sourced recipe'
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "sourced recipe"

data/features/recipe/target.feature

@@ -1,23 +0,0 @@
-Feature: `target' recipe keyword
-
-  Scenario: registers the target host on which tasks should be applied
-    Given a recipe with:
-      """
-      target 'some_host.example'
-
-      task :some_task do
-        echo env.target
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_host.example"
-
-  Scenario: returns current target when no arguments are provided
-    Given a recipe with:
-      """
-      target 'some_host.example'
-
-      env.output.puts target
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_host.example"

data/features/recipe/test_macro.feature

@@ -1,50 +0,0 @@
-Feature: `test_macro' recipe keyword
-
-  Scenario: declares a new test keyword
-    Given a recipe with:
-      """
-      test_macro :even? do |n|
-        n % 2 == 0
-      end
-
-      [1, 2].each do |n|
-        task "test_macro-even-#{n}" do
-          condition { even? n }
-          echo n
-        end
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "2"
-    And the output must not contain "1"
-
-  @sshd
-  Scenario: has access to core tests
-    Given a recipe with:
-      """
-      test_macro(:other_env?) { |k| env? k }
-
-      [:shell, :non_existent_var].each do |k|
-        task "test_macro-condition-#{k}" do
-          condition { other_env? k }
-          echo "#{k}_ok"
-        end
-      end
-      """
-    When I successfully execute the recipe on remote target
-    Then the output must contain "shell_ok"
-    Then the output must not contain "non_existent_var_ok"
-
-  Scenario: has access to other tests declared with `test_macro'
-    Given a recipe with:
-      """
-      test_macro(:one?)       { |e| e == 1 }
-      test_macro(:one_alias?) { |e| one? e }
-
-      task :test_macro_macro do
-        condition { one_alias? 1 }
-        echo 'one_alias_ok'
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must contain "one_alias_ok"

data/features/ssh/config.feature

@@ -1,25 +0,0 @@
-Feature: SSH settings
-
-  Background:
-    Given a recipe with:
-      """
-      target 'some_host.example'
-
-      task :some_task do
-        echo env.remote.user_name
-      end
-      """
-
-  Scenario: uses current user login name as SSH user name by default
-    When I successfully execute the recipe
-    Then the output must contain my current login name
-
-  @mocked-home-directory
-  Scenario: uses configured SSH user name for a given host
-    Given an SSH config with:
-      """
-      Host some_host.example
-        User some_user
-      """
-    When I successfully execute the recipe
-    Then the output must contain "some_user"

data/features/steps/environment_steps.rb

@@ -1,3 +0,0 @@
-Given /^I set the environment variable "([^"]+)"$/ do |variable|
-  set_environment_variable variable, 'yes'
-end

data/features/support/env.rb

@@ -1 +0,0 @@
-require 'producer/core/testing/cucumber'

data/features/task/ask.feature

@@ -1,23 +0,0 @@
-Feature: `ask' task keyword
-
-  @exec
-  Scenario: prompts user with a list of choices on standard output
-    Given a recipe with:
-      """
-      task :ask_letter do
-        letter = ask 'Which letter?', [[:a, ?A], [:b, ?B]]
-
-        echo letter.inspect
-      end
-      """
-    When I execute the recipe interactively
-    And I type "1"
-    Then the output must contain:
-      """
-      Which letter?
-      0: A
-      1: B
-      Choice:
-      :b
-      """
-    And the exit status must be 0

data/features/task/condition.feature

@@ -1,13 +0,0 @@
-Feature: `condition' task keyword
-
-  Scenario: prevents task actions application when condition is not met
-    Given a recipe with:
-      """
-      task :some_task do
-        condition { false }
-
-        echo 'evaluated'
-      end
-      """
-    When I successfully execute the recipe
-    Then the output must not contain "evaluated"

data/features/task/nested_tasks.feature

@@ -1,20 +0,0 @@
-Feature: nested tasks
-
-  Background:
-    Given a recipe with:
-      """
-      task :outer_task do
-        task :inner_task do
-          echo 'OK'
-        end
-      end
-      """
-
-    Scenario: applies nested tasks
-      When I successfully execute the recipe
-      Then the output must match /\AOK/
-
-    Scenario: indents logging from nested tasks
-      When I successfully execute the recipe with option -v
-      Then the output must match /^  Task:.+/
-      And the output must match /^   action:.+/

data/features/task/recipe_argv.feature

@@ -1,13 +0,0 @@
-Feature: `recipe_argv' task keyword
-
-  Background:
-    Given a recipe with:
-      """
-      task :echo_arguments do
-        echo recipe_argv
-      end
-      """
-
-  Scenario: returns recipe arguments
-    When I successfully execute the recipe with arguments "foo bar"
-    Then the output must contain exactly "foo\nbar\n"

data/features/task/target.feature

@@ -1,11 +0,0 @@
-Feature: `target' task keyword
-
-  Scenario: returns the current target
-    Given a recipe with:
-      """
-      target 'some_host.example'
-
-      task(:echo_target) { echo target }
-      """
-    When I execute the recipe
-    Then the output must contain "some_host.example"

data/features/task/template.feature

@@ -1,49 +0,0 @@
-Feature: `template' task keyword
-
-  Scenario: renders an ERB template file
-    Given a file named "templates/basic.erb" with:
-      """
-      basic template
-      """
-    And a recipe with:
-      """
-      task(:echo_template) { echo template 'basic' }
-      """
-    When I execute the recipe
-    Then the output must contain "basic template"
-
-  Scenario: renders ERB with given attributes as member data
-    Given a file named "templates/variables.erb" with:
-      """
-      <%= @foo %>
-      """
-    And a recipe with:
-      """
-      task(:echo_template) { echo template('variables', foo: 'bar') }
-      """
-    When I execute the recipe
-    Then the output must contain "bar"
-
-  Scenario: renders without `templates' search path
-    Given a file named "templates/basic.erb" with:
-      """
-      basic template
-      """
-    And a recipe with:
-      """
-      task(:echo_template) { echo template './templates/basic' }
-      """
-    When I execute the recipe
-    Then the output must contain "basic template"
-
-  Scenario: parses a yaml file
-    Given a file named "templates/basic.yaml" with:
-      """
-      foo: bar
-      """
-    And a recipe with:
-      """
-      task(:echo_template) { echo template('basic')['foo'] }
-      """
-    When I execute the recipe
-    Then the output must match /^bar$/

data/features/tests/dir.feature

@@ -1,21 +0,0 @@
-@sshd
-Feature: `dir?' condition keyword
-
-  Background:
-    Given a recipe with:
-      """
-      task :dir_test do
-        condition { dir? 'some_directory' }
-
-        echo 'evaluated'
-      end
-      """
-
-  Scenario: succeeds when directory exists
-    Given a remote directory named "some_directory"
-    When I successfully execute the recipe on remote target
-    Then the output must contain "evaluated"
-
-  Scenario: fails when directory does not exist
-    When I successfully execute the recipe on remote target
-    Then the output must not contain "evaluated"

data/features/tests/env.feature

@@ -1,47 +0,0 @@
-@sshd
-Feature: `env?' condition keyword
-
-  Background:
-    Given a recipe with:
-      """
-      task :env_test_definition_ok do
-        condition { env? :shell }
-
-        echo 'definition_ok'
-      end
-
-      task :env_test_definition_ko do
-        condition { env? :non_existent_var }
-
-        echo 'definition_ko'
-      end
-
-      task :env_test_value do
-        condition { env? :shell, '/bin/sh' }
-
-        echo 'value_ok'
-      end
-
-      task :env_test_value do
-        condition { env? :shell, 'non_existent_shell' }
-
-        echo 'value_ko'
-      end
-      """
-
-  Scenario: succeeds when remote environment variable is defined
-    When I successfully execute the recipe on remote target
-    Then the output must contain "definition_ok"
-
-  Scenario: fails when remote environment variable is not defined
-    When I successfully execute the recipe on remote target
-    Then the output must not contain "definition_ko"
-
-  @ci_skip
-  Scenario: succeeds when remote environment variable value match
-    When I successfully execute the recipe on remote target
-    Then the output must contain "value_ok"
-
-  Scenario: fails when remote environment variable value does not match
-    When I successfully execute the recipe on remote target
-    Then the output must not contain "value_ko"

data/features/tests/executable.feature

@@ -1,26 +0,0 @@
-@sshd
-Feature: `executable?' condition keyword
-
-  Background:
-    Given a recipe with:
-      """
-      task :executable_test_ok do
-        condition { executable? 'true' }
-
-        echo 'test_ok'
-      end
-
-      task :executable_test_ok do
-        condition { executable? 'some_non_existent_executable' }
-
-        echo 'test_ko'
-      end
-      """
-
-  Scenario: succeeds when remote executable is available
-    When I successfully execute the recipe on remote target
-    Then the output must contain "test_ok"
-
-  Scenario: fails when remote executable is not available
-    When I successfully execute the recipe on remote target
-    Then the output must not contain "test_ko"