test-kitchen 1.6.0 → 1.7.0

data/features/kitchen_command.feature

@@ -1,16 +1,16 @@
-Feature: A command line interface for Test Kitchen
-  In order to provide a quick and response development workflow
-  As a Test Kitchen user
-  I want a command line interface that has sane defaults and built in help
-
-  @spawn
-  Scenario: Displaying help
-    When I run `kitchen help`
-    Then the exit status should be 0
-    And the output should contain "kitchen console"
-    And the output should contain "kitchen version"
-
-  Scenario: Displaying the version of Test Kitchen
-    When I run `kitchen version`
-    Then the exit status should be 0
-    And the output should contain "Test Kitchen version"
+Feature: A command line interface for Test Kitchen
+  In order to provide a quick and response development workflow
+  As a Test Kitchen user
+  I want a command line interface that has sane defaults and built in help
+
+  @spawn
+  Scenario: Displaying help
+    When I run `kitchen help`
+    Then the exit status should be 0
+    And the output should contain "kitchen console"
+    And the output should contain "kitchen version"
+
+  Scenario: Displaying the version of Test Kitchen
+    When I run `kitchen version`
+    Then the exit status should be 0
+    And the output should contain "Test Kitchen version"

data/features/kitchen_console_command.feature

@@ -1,34 +1,34 @@
-Feature: Running a console command
-  In order to interactively explore Kitchen's internals and wiring
-  As an opterator
-  I want to run a command to launch an interactive console session
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    platforms:
-      - name: flebian
-
-    suites:
-      - name: default
-      - name: full
-    """
-
-  @spawn
-  Scenario: Launching a session
-    When I run `kitchen console` interactively
-    And I type "instances.map { |i| i.name }"
-    And I type "exit"
-    Then the output should contain "kc(Kitchen::Config)> "
-    Then the output should contain:
-    """
-    ["default-flebian", "full-flebian"]
-    """
-    And the exit status should be 0
+Feature: Running a console command
+  In order to interactively explore Kitchen's internals and wiring
+  As an opterator
+  I want to run a command to launch an interactive console session
+
+  Background:
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver:
+      name: dummy
+
+    provisioner:
+      name: dummy
+
+    platforms:
+      - name: flebian
+
+    suites:
+      - name: default
+      - name: full
+    """
+
+  @spawn
+  Scenario: Launching a session
+    When I run `kitchen console` interactively
+    And I type "instances.map { |i| i.name }"
+    And I type "exit"
+    Then the output should contain "kc(Kitchen::Config)> "
+    Then the output should contain:
+    """
+    ["default-flebian", "full-flebian"]
+    """
+    And the exit status should be 0

data/features/kitchen_defaults.feature

@@ -1,38 +1,38 @@
-Feature: Test Kitchen defaults
-  In order to have a more pleasant out of the box experience
-  As a user of Test Kitchen
-  I want to have some common defaults handled for me
-
-  Scenario: Windows platforms get the Winrm Transport by default
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver: dummy
-    provisioner: dummy
-    verifier: dummy
-
-    platforms:
-      - name: win-8.1
-
-    suites:
-      - name: default
-    """
-    When I successfully run `kitchen list`
-    Then the output should match /^default-win-81\s+Dummy\s+Dummy\s+Dummy\s+Winrm\s+\<Not Created\>$/
-
-  Scenario: Non-Windows platforms get the Ssh Transport by default
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver: dummy
-    provisioner: dummy
-    verifier: dummy
-
-    platforms:
-      - name: ubuntu-14.04
-
-    suites:
-      - name: default
-    """
-    When I successfully run `kitchen list`
-    Then the output should match /^default-ubuntu-1404\s+Dummy\s+Dummy\s+Dummy\s+Ssh\s+\<Not Created\>$/
+Feature: Test Kitchen defaults
+  In order to have a more pleasant out of the box experience
+  As a user of Test Kitchen
+  I want to have some common defaults handled for me
+
+  Scenario: Windows platforms get the Winrm Transport by default
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver: dummy
+    provisioner: dummy
+    verifier: dummy
+
+    platforms:
+      - name: win-8.1
+
+    suites:
+      - name: default
+    """
+    When I successfully run `kitchen list`
+    Then the output should match /^default-win-81\s+Dummy\s+Dummy\s+Dummy\s+Winrm\s+\<Not Created\>$/
+
+  Scenario: Non-Windows platforms get the Ssh Transport by default
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver: dummy
+    provisioner: dummy
+    verifier: dummy
+
+    platforms:
+      - name: ubuntu-14.04
+
+    suites:
+      - name: default
+    """
+    When I successfully run `kitchen list`
+    Then the output should match /^default-ubuntu-1404\s+Dummy\s+Dummy\s+Dummy\s+Ssh\s+\<Not Created\>$/

data/features/kitchen_diagnose_command.feature

@@ -1,96 +1,96 @@
-Feature: Running a diagnosis command
-  In order to understand how Kitchen is wired together
-  As an operator and configuration sleuth
-  I want to run a command to get configuration information
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    transport:
-      name: dummy
-
-    verifier:
-      name: dummy
-
-    platforms:
-      - name: cool
-      - name: beans
-
-    suites:
-      - name: client
-      - name: server
-    """
-
-  @spawn
-  Scenario: Displaying help
-    When I run `kitchen help diagnose`
-    Then the output should contain:
-    """
-    Usage:
-      kitchen diagnose
-    """
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Showing all instances
-    When I run `kitchen diagnose`
-    Then the output should contain "timestamp: "
-    Then the output should contain "kitchen_version: "
-    Then the output should contain "  client-cool:"
-    Then the output should contain "  client-beans:"
-    Then the output should contain "  server-cool:"
-    Then the output should contain "  server-beans:"
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Showing all instances with loader configuration
-    When I run `kitchen diagnose --loader`
-    Then the output should contain:
-    """
-    loader:
-      process_erb: true
-      process_local: true
-      process_global: true
-    """
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Showing all instances with plugin configuration
-    When I run `kitchen diagnose --plugins`
-    Then the output should contain "plugins:"
-    Then the output should contain "    class: Kitchen::Driver::Dummy"
-    Then the output should contain "    class: Kitchen::Provisioner::Dummy"
-    Then the output should contain "    class: Kitchen::Transport::Dummy"
-    Then the output should contain "    class: Kitchen::Verifier::Dummy"
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Coping with loading failure
-    Given a file named ".kitchen.local.yml" with:
-    """
-    I'm a little teapot
-    """
-    When I run `kitchen diagnose --all`
-    Then the output should contain:
-    """
-        raw_data:
-          error:
-    """
-    And the output should contain:
-    """
-    instances:
-      error:
-    """
-    And the output should contain:
-    """
-    plugins:
-      error:
-    """
-    And the exit status should be 0
+Feature: Running a diagnosis command
+  In order to understand how Kitchen is wired together
+  As an operator and configuration sleuth
+  I want to run a command to get configuration information
+
+  Background:
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver:
+      name: dummy
+
+    provisioner:
+      name: dummy
+
+    transport:
+      name: dummy
+
+    verifier:
+      name: dummy
+
+    platforms:
+      - name: cool
+      - name: beans
+
+    suites:
+      - name: client
+      - name: server
+    """
+
+  @spawn
+  Scenario: Displaying help
+    When I run `kitchen help diagnose`
+    Then the output should contain:
+    """
+    Usage:
+      kitchen diagnose
+    """
+    And the exit status should be 0
+
+  @spawn
+  Scenario: Showing all instances
+    When I run `kitchen diagnose`
+    Then the output should contain "timestamp: "
+    Then the output should contain "kitchen_version: "
+    Then the output should contain "  client-cool:"
+    Then the output should contain "  client-beans:"
+    Then the output should contain "  server-cool:"
+    Then the output should contain "  server-beans:"
+    And the exit status should be 0
+
+  @spawn
+  Scenario: Showing all instances with loader configuration
+    When I run `kitchen diagnose --loader`
+    Then the output should contain:
+    """
+    loader:
+      process_erb: true
+      process_local: true
+      process_global: true
+    """
+    And the exit status should be 0
+
+  @spawn
+  Scenario: Showing all instances with plugin configuration
+    When I run `kitchen diagnose --plugins`
+    Then the output should contain "plugins:"
+    Then the output should contain "    class: Kitchen::Driver::Dummy"
+    Then the output should contain "    class: Kitchen::Provisioner::Dummy"
+    Then the output should contain "    class: Kitchen::Transport::Dummy"
+    Then the output should contain "    class: Kitchen::Verifier::Dummy"
+    And the exit status should be 0
+
+  @spawn
+  Scenario: Coping with loading failure
+    Given a file named ".kitchen.local.yml" with:
+    """
+    I'm a little teapot
+    """
+    When I run `kitchen diagnose --all`
+    Then the output should contain:
+    """
+        raw_data:
+          error:
+    """
+    And the output should contain:
+    """
+    instances:
+      error:
+    """
+    And the output should contain:
+    """
+    plugins:
+      error:
+    """
+    And the exit status should be 0

data/features/kitchen_driver_create_command.feature

@@ -1,64 +1,64 @@
-Feature: Create a new Test Kitchen Driver project
-  In order to make plugin development a snap
-  As a user of Test Kitchen
-  I want a command to run that will give me a driver gem project scaffold
-
-  @spawn
-  Scenario: Displaying help
-    When I run `kitchen help driver create`
-    Then the output should contain:
-    """
-    Usage:
-      kitchen driver create [NAME]
-    """
-    And the exit status should be 0
-
-  Scenario: Running with default values
-    When I run `kitchen driver create qemu`
-    Then a directory named "kitchen-qemu" should exist
-    And the file "kitchen-qemu/CHANGELOG.md" should contain:
-    """
-    ## 0.1.0 / Unreleased
-    """
-    And the file "kitchen-qemu/Gemfile" should contain "gemspec"
-    And the file "kitchen-qemu/Rakefile" should contain "task :stats"
-    And the file "kitchen-qemu/README.md" should contain:
-    """
-    Kitchen::Qemu
-    """
-    And the file "kitchen-qemu/kitchen-qemu.gemspec" should contain:
-    """
-    require 'kitchen/driver/qemu_version'
-    """
-    And the file "kitchen-qemu/LICENSE" should contain:
-    """
-    Licensed under the Apache License, Version 2.0
-    """
-    And the file "kitchen-qemu/.gitignore" should contain:
-    """
-    Gemfile.lock
-    """
-    And the file "kitchen-qemu/.tailor" should contain:
-    """
-    config.file_set 'lib/**/*.rb'
-    """
-    And the file "kitchen-qemu/.travis.yml" should contain:
-    """
-    language: ruby
-    """
-    And a file named "kitchen-qemu/.cane" should exist
-    And the file "kitchen-qemu/lib/kitchen/driver/qemu_version.rb" should contain:
-    """
-    QEMU_VERSION = "0.1.0.dev"
-    """
-    And the file "kitchen-qemu/lib/kitchen/driver/qemu.rb" should contain:
-    """
-    class Qemu < Kitchen::Driver::SSHBase
-    """
-
-  Scenario: Running with an alternate license
-    When I successfully run `kitchen driver create foo --license=reserved`
-    Then the file "kitchen-foo/LICENSE" should contain:
-    """
-    All rights reserved - Do Not Redistribute
-    """
+Feature: Create a new Test Kitchen Driver project
+  In order to make plugin development a snap
+  As a user of Test Kitchen
+  I want a command to run that will give me a driver gem project scaffold
+
+  @spawn
+  Scenario: Displaying help
+    When I run `kitchen help driver create`
+    Then the output should contain:
+    """
+    Usage:
+      kitchen driver create [NAME]
+    """
+    And the exit status should be 0
+
+  Scenario: Running with default values
+    When I run `kitchen driver create qemu`
+    Then a directory named "kitchen-qemu" should exist
+    And the file "kitchen-qemu/CHANGELOG.md" should contain:
+    """
+    ## 0.1.0 / Unreleased
+    """
+    And the file "kitchen-qemu/Gemfile" should contain "gemspec"
+    And the file "kitchen-qemu/Rakefile" should contain "task :stats"
+    And the file "kitchen-qemu/README.md" should contain:
+    """
+    Kitchen::Qemu
+    """
+    And the file "kitchen-qemu/kitchen-qemu.gemspec" should contain:
+    """
+    require 'kitchen/driver/qemu_version'
+    """
+    And the file "kitchen-qemu/LICENSE" should contain:
+    """
+    Licensed under the Apache License, Version 2.0
+    """
+    And the file "kitchen-qemu/.gitignore" should contain:
+    """
+    Gemfile.lock
+    """
+    And the file "kitchen-qemu/.tailor" should contain:
+    """
+    config.file_set 'lib/**/*.rb'
+    """
+    And the file "kitchen-qemu/.travis.yml" should contain:
+    """
+    language: ruby
+    """
+    And a file named "kitchen-qemu/.cane" should exist
+    And the file "kitchen-qemu/lib/kitchen/driver/qemu_version.rb" should contain:
+    """
+    QEMU_VERSION = "0.1.0.dev"
+    """
+    And the file "kitchen-qemu/lib/kitchen/driver/qemu.rb" should contain:
+    """
+    class Qemu < Kitchen::Driver::SSHBase
+    """
+
+  Scenario: Running with an alternate license
+    When I successfully run `kitchen driver create foo --license=reserved`
+    Then the file "kitchen-foo/LICENSE" should contain:
+    """
+    All rights reserved - Do Not Redistribute
+    """