cape 1.6.2 → 1.7.0

data/features/dsl/mirror_rake_tasks/with_defined_task_and_valid_options_and_cd_and_environment_variables.feature

@@ -0,0 +1,48 @@
+Feature: The #mirror_rake_tasks DSL method with a defined task, valid options, a different directory, and environment variables
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror only the matching Rake task
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      Cape do
+        mirror_rake_tasks :with_period do |recipes|
+          recipes.options[:roles] = :app
+          recipes.cd { release_path }
+          recipes.env['RAILS_ENV'] = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap -vT`
+    Then the output should contain:
+      """
+      cap with_period # Ends with period.
+      """
+    And the output should not contain "without_period"
+    And the output should not contain "my_namespace"
+
+  Scenario: mirror the matching Rake task with its implementation
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      set :release_path, '/release/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks :with_period do |recipes|
+          recipes.options[:roles] = :app
+          recipes.cd { release_path }
+          recipes.env['RAILS_ENV'] = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap with_period`
+    Then the output should contain:
+      """
+        * executing `with_period'
+        * executing "cd /release/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake with_period RAILS_ENV=\"rails-env\""
+      `with_period' is only run for servers matching {:roles=>:app}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_defined_task_and_valid_options_and_environment_variables.feature

@@ -0,0 +1,98 @@
+Feature: The #mirror_rake_tasks DSL method with a defined task, valid options, and environment variables
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  @deprecated
+  Scenario: mirror only the matching Rake task (deprecated)
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      Cape do
+        mirror_rake_tasks :with_period, :roles => :app do |env|
+          env['RAILS_ENV'] = rails_env
+        end
+      end
+      """
+    When I run `cap -vT`
+    Then the output should contain:
+      """
+      cap with_period # Ends with period.
+      """
+    And the output should not contain "without_period"
+    And the output should not contain "my_namespace"
+    And the output should contain:
+      """
+      *** DEPRECATED: `mirror_rake_tasks :with_period, :roles => :app`. Use this instead: `mirror_rake_tasks(:with_period) { |recipes| recipes.options[:roles] = :app }`
+      """
+    And the output should contain:
+      """
+      *** DEPRECATED: Referencing Capistrano variables from Cape without wrapping them in a block, a lambda, or another callable object
+      """
+
+  Scenario: mirror only the matching Rake task
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      Cape do
+        mirror_rake_tasks :with_period do |recipes|
+          recipes.options[:roles] = :app
+          recipes.env['RAILS_ENV'] = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap -vT`
+    Then the output should contain:
+      """
+      cap with_period # Ends with period.
+      """
+    And the output should not contain "without_period"
+    And the output should not contain "my_namespace"
+    And the output should not contain "DEPRECATED"
+
+  @deprecated
+  Scenario: mirror the matching Rake task with its implementation (deprecated)
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks 'with_period', :roles => :app do |env|
+          env['RAILS_ENV'] = rails_env
+        end
+      end
+      """
+    When I run `cap with_period`
+    Then the output should contain:
+      """
+      *** DEPRECATED: `mirror_rake_tasks("with_period", :roles => :app) { |env| env["RAILS_ENV"] = "rails-env" }`. Use this instead: `mirror_rake_tasks("with_period") { |recipes| recipes.options[:roles] = :app; recipes.env["RAILS_ENV"] = "rails-env" }`
+        * executing `with_period'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake with_period RAILS_ENV=\"rails-env\""
+      `with_period' is only run for servers matching {:roles=>:app}, but no servers matched
+      """
+
+  Scenario: mirror the matching Rake task with its implementation
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks 'with_period' do |recipes|
+          recipes.options[:roles] = :app
+          recipes.env['RAILS_ENV'] = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap with_period`
+    Then the output should contain:
+      """
+        * executing `with_period'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake with_period RAILS_ENV=\"rails-env\""
+      `with_period' is only run for servers matching {:roles=>:app}, but no servers matched
+      """
+    And the output should not contain "DEPRECATED"

data/features/dsl/mirror_rake_tasks/with_environment_variables.feature

@@ -4,12 +4,43 @@ Feature: The #mirror_rake_tasks DSL method with environment variables
   As a developer using Cape,
   I want to use the Cape DSL.
 
-  Scenario: mirror a Rake task with its implementation
+  @deprecated
+  Scenario: mirror only the matching Rake task (deprecated)
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      Cape do
+        mirror_rake_tasks do |env|
+          env['RAILS_ENV'] = rails_env
+        end
+      end
+      """
+    When I run `cap -vT`
+    And the output should contain:
+      """
+      *** DEPRECATED: Referencing Capistrano variables from Cape without wrapping them in a block, a lambda, or another callable object
+      """
+
+  Scenario: mirror only the matching Rake task
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.env['RAILS_ENV'] = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap -vT`
+    And the output should not contain "DEPRECATED"
+
+  @deprecated
+  Scenario: mirror a Rake task with its implementation (deprecated)
     Given a full-featured Rakefile
     And a Capfile with:
       """
-      set :current_path, '/path/to/current/deployed/application'
-      set :rails_env,    'production'
+      set :current_path, '/current/path'
+      set :rails_env,    'rails-env'
 
       Cape do
         mirror_rake_tasks do |env|
@@ -21,9 +52,35 @@ Feature: The #mirror_rake_tasks DSL method with environment variables
       end
       """
     When I run `cap with_period`
+    Then the output should contain:
+      """
+      *** DEPRECATED: `mirror_rake_tasks { |env| env["RAILS_ENV"] = "rails-env"; env[nil] = "foo"; env["FOO"] = nil; env["SOME_OTHER"] = "var" }`. Use this instead: `mirror_rake_tasks { |recipes| recipes.env["RAILS_ENV"] = "rails-env"; recipes.env[nil] = "foo"; recipes.env["FOO"] = nil; recipes.env["SOME_OTHER"] = "var" }`
+        * executing `with_period'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake with_period RAILS_ENV=\"rails-env\" SOME_OTHER=\"var\""
+      `with_period' is only run for servers matching {}, but no servers matched
+      """
+
+  Scenario: mirror a Rake task with its implementation
+    Given a full-featured Rakefile
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.env['RAILS_ENV']  = lambda { rails_env }
+          recipes.env[nil]          = 'foo'
+          recipes.env['FOO']        = nil
+          recipes.env['SOME_OTHER'] = 'var'
+        end
+      end
+      """
+    When I run `cap with_period`
     Then the output should contain:
       """
         * executing `with_period'
-        * executing "cd /path/to/current/deployed/application && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake with_period RAILS_ENV=\"production\" SOME_OTHER=\"var\""
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake with_period RAILS_ENV=\"rails-env\" SOME_OTHER=\"var\""
       `with_period' is only run for servers matching {}, but no servers matched
       """
+    And the output should not contain "DEPRECATED"

data/features/dsl/mirror_rake_tasks/with_rename.feature

@@ -0,0 +1,27 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load"
+      `do_load' is only run for servers matching {}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_cd.feature

@@ -0,0 +1,28 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic and a different directory
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :release_path, '/release/path'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.cd { release_path }
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /release/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load"
+      `do_load' is only run for servers matching {}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_cd_and_environment_variables.feature

@@ -0,0 +1,30 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic, a different directory, and environment variables
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :release_path, '/release/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.cd { release_path }
+          recipes.env['RAILS_ENV']  = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /release/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load RAILS_ENV=\"rails-env\""
+      `do_load' is only run for servers matching {}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_environment_variables.feature

@@ -0,0 +1,29 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic and environment variables
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.env['RAILS_ENV']  = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load RAILS_ENV=\"rails-env\""
+      `do_load' is only run for servers matching {}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_valid_options.feature

@@ -0,0 +1,28 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic and valid options
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.options[:roles] = :app
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load"
+      `do_load' is only run for servers matching {:roles=>:app}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_valid_options_and_cd.feature

@@ -0,0 +1,29 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic, valid options, and a different directory
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :release_path, '/release/path'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.options[:roles] = :app
+          recipes.cd { release_path }
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /release/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load"
+      `do_load' is only run for servers matching {:roles=>:app}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_valid_options_and_cd_and_environment_variables.feature

@@ -0,0 +1,31 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic, valid options, a different directory, and enviroment variables
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :release_path, '/release/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.options[:roles] = :app
+          recipes.cd { release_path }
+          recipes.env['RAILS_ENV']  = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /release/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load RAILS_ENV=\"rails-env\""
+      `do_load' is only run for servers matching {:roles=>:app}, but no servers matched
+      """

data/features/dsl/mirror_rake_tasks/with_rename_and_valid_options_and_environment_variables.feature

@@ -0,0 +1,30 @@
+Feature: The #mirror_rake_tasks DSL method with renaming logic, valid options, and enviroment variables
+
+  In order to include Rake tasks with descriptions in my Capistrano recipes,
+  As a developer using Cape,
+  I want to use the Cape DSL.
+
+  Scenario: mirror a Ruby-method-shadowing Rake task with its implementation
+    Given a full-featured Rakefile defining a Ruby-method-shadowing task
+    And a Capfile with:
+      """
+      set :current_path, '/current/path'
+      set :rails_env,    'rails-env'
+
+      Cape do
+        mirror_rake_tasks do |recipes|
+          recipes.rename do |task_name|
+            "do_#{task_name}"
+          end
+          recipes.options[:roles] = :app
+          recipes.env['RAILS_ENV']  = lambda { rails_env }
+        end
+      end
+      """
+    When I run `cap do_load`
+    Then the output should contain:
+      """
+        * executing `do_load'
+        * executing "cd /current/path && /usr/bin/env `/usr/bin/env bundle check >/dev/null 2>&1; case $? in 0|1 ) echo bundle exec ;; esac` rake load RAILS_ENV=\"rails-env\""
+      `do_load' is only run for servers matching {:roles=>:app}, but no servers matched
+      """