test-kitchen 1.6.0 → 1.7.0

data/features/kitchen_list_command.feature

@@ -1,104 +1,104 @@
-Feature: Listing Test Kitchen instances
-  In order to understand how the .kitchen.yml is consumed
-  As a user of Test Kitchen
-  I want to run a command to see the state of my instances
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver: dummy
-    provisioner: chef_solo
-
-    platforms:
-      - name: ubuntu-13.04
-      - name: centos-6.4
-      - name: centos-6.4-with-small-mem
-
-    suites:
-      - name: foobar
-    """
-
-  Scenario: Listing instances
-    When I run `kitchen list`
-    Then the exit status should be 0
-    And the output should match /^foobar-ubuntu-1304\s+Dummy\s+ChefSolo\s+Busser\s+Ssh\s+\<Not Created\>$/
-    And the output should match /^foobar-centos-64\s+Dummy\s+ChefSolo\s+Busser\s+Ssh\s+\<Not Created\>$/
-
-  Scenario: Listing instances with the --bare option
-    When I run `kitchen list --bare`
-    Then the exit status should be 0
-    And the output should contain exactly:
-    """
-    foobar-ubuntu-1304
-    foobar-centos-64
-    foobar-centos-64-with-small-mem
-
-    """
-
-  Scenario: Listing instances with a simple regular expression glob
-    When I successfully run `kitchen list ubun --bare`
-    Then the output should contain exactly:
-    """
-    foobar-ubuntu-1304
-
-    """
-
-  Scenario: Listing instances with a Ruby regular expression glob, requiring
-    signle quoting on the command line
-    When I successfully run `kitchen list '^foo.*\-(10|13)04$' --bare`
-    Then the output should contain exactly:
-    """
-    foobar-ubuntu-1304
-
-    """
-
-  @spawn
-  Scenario: Listing instances with a regular expression yielding no results
-    When I run `kitchen list freebsd --bare`
-    Then the exit status should not be 0
-    And the output should contain "No instances for regex `freebsd', try running `kitchen list'"
-
-  @spawn
-  Scenario: Listing instances with a bad regular expression
-    When I run `kitchen list *centos* --bare`
-    Then the exit status should not be 0
-    And the output should contain "Invalid Ruby regular expression"
-
-  Scenario: Listing a full instance name returns an exact match, not fuzzy matches
-    When I successfully run `kitchen list  foobar-centos-64 --bare`
-    Then the output should contain exactly:
-    """
-    foobar-centos-64
-
-    """
-
-  Scenario: Listing a full instance name returns an exact match, not fuzzy matches at start
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver: dummy
-    provisioner: chef_solo
-
-    platforms:
-      - name: ubuntu-12.04
-
-    suites:
-      - name: gdb01-master
-      - name: logdb01-master
-    """
-    When I successfully run `kitchen list gdb01-master-ubuntu-1204 --bare`
-    Then the output should contain exactly:
-    """
-    gdb01-master-ubuntu-1204
-
-    """
-
-  Scenario: Listing a full instance with regex returns all regex matches
-    When I successfully run `kitchen list  'foobar-centos-64.*' --bare`
-    Then the output should contain exactly:
-    """
-    foobar-centos-64
-    foobar-centos-64-with-small-mem
-
-    """
+Feature: Listing Test Kitchen instances
+  In order to understand how the .kitchen.yml is consumed
+  As a user of Test Kitchen
+  I want to run a command to see the state of my instances
+
+  Background:
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver: dummy
+    provisioner: chef_solo
+
+    platforms:
+      - name: ubuntu-13.04
+      - name: centos-6.4
+      - name: centos-6.4-with-small-mem
+
+    suites:
+      - name: foobar
+    """
+
+  Scenario: Listing instances
+    When I run `kitchen list`
+    Then the exit status should be 0
+    And the output should match /^foobar-ubuntu-1304\s+Dummy\s+ChefSolo\s+Busser\s+Ssh\s+\<Not Created\>$/
+    And the output should match /^foobar-centos-64\s+Dummy\s+ChefSolo\s+Busser\s+Ssh\s+\<Not Created\>$/
+
+  Scenario: Listing instances with the --bare option
+    When I run `kitchen list --bare`
+    Then the exit status should be 0
+    And the output should contain exactly:
+    """
+    foobar-ubuntu-1304
+    foobar-centos-64
+    foobar-centos-64-with-small-mem
+
+    """
+
+  Scenario: Listing instances with a simple regular expression glob
+    When I successfully run `kitchen list ubun --bare`
+    Then the output should contain exactly:
+    """
+    foobar-ubuntu-1304
+
+    """
+
+  Scenario: Listing instances with a Ruby regular expression glob, requiring
+    signle quoting on the command line
+    When I successfully run `kitchen list '^foo.*\-(10|13)04$' --bare`
+    Then the output should contain exactly:
+    """
+    foobar-ubuntu-1304
+
+    """
+
+  @spawn
+  Scenario: Listing instances with a regular expression yielding no results
+    When I run `kitchen list freebsd --bare`
+    Then the exit status should not be 0
+    And the output should contain "No instances for regex `freebsd', try running `kitchen list'"
+
+  @spawn
+  Scenario: Listing instances with a bad regular expression
+    When I run `kitchen list *centos* --bare`
+    Then the exit status should not be 0
+    And the output should contain "Invalid Ruby regular expression"
+
+  Scenario: Listing a full instance name returns an exact match, not fuzzy matches
+    When I successfully run `kitchen list  foobar-centos-64 --bare`
+    Then the output should contain exactly:
+    """
+    foobar-centos-64
+
+    """
+
+  Scenario: Listing a full instance name returns an exact match, not fuzzy matches at start
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver: dummy
+    provisioner: chef_solo
+
+    platforms:
+      - name: ubuntu-12.04
+
+    suites:
+      - name: gdb01-master
+      - name: logdb01-master
+    """
+    When I successfully run `kitchen list gdb01-master-ubuntu-1204 --bare`
+    Then the output should contain exactly:
+    """
+    gdb01-master-ubuntu-1204
+
+    """
+
+  Scenario: Listing a full instance with regex returns all regex matches
+    When I successfully run `kitchen list  'foobar-centos-64.*' --bare`
+    Then the output should contain exactly:
+    """
+    foobar-centos-64
+    foobar-centos-64-with-small-mem
+
+    """

data/features/kitchen_login_command.feature

@@ -1,62 +1,62 @@
-Feature: Logging into a Kitchen instance
-  In order to iterate, explore, and debug
-  As a crafty developer
-  I want to run a command that will give me a terminal session
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    transport:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    platforms:
-      - name: flebian
-
-    suites:
-      - name: default
-      - name: full
-    """
-    And I successfully run `kitchen create default-flebian`
-
-  @spawn
-  Scenario: Logging in to an instance
-    When I run `kitchen login default-flebian`
-    Then the output should contain:
-    """
-    Remote login not supported in Kitchen::Transport::Dummy::Connection.
-    """
-    And the exit status should not be 0
-
-  @spawn
-  Scenario: Attempting to log into a non-created instance
-    When I run `kitchen login full-flebian`
-    Then the output should contain:
-    """
-    Instance <full-flebian> has not yet been created
-    """
-    And the exit status should not be 0
-
-  @spawn
-  Scenario: Attempting to log into a non-existent instance
-    When I run `kitchen login nope`
-    Then the output should contain "No instances for regex `nope'"
-    And the exit status should not be 0
-
-  @spawn
-  Scenario: Attempting to log into an instance with an overly fuzzy match
-    When I run `kitchen login flebian`
-    Then the output should contain:
-    """
-    Argument `flebian' returned multiple results:
-      * default-flebian
-      * full-flebian
-    """
-    And the exit status should not be 0
-
+Feature: Logging into a Kitchen instance
+  In order to iterate, explore, and debug
+  As a crafty developer
+  I want to run a command that will give me a terminal session
+
+  Background:
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver:
+      name: dummy
+
+    transport:
+      name: dummy
+
+    provisioner:
+      name: dummy
+
+    platforms:
+      - name: flebian
+
+    suites:
+      - name: default
+      - name: full
+    """
+    And I successfully run `kitchen create default-flebian`
+
+  @spawn
+  Scenario: Logging in to an instance
+    When I run `kitchen login default-flebian`
+    Then the output should contain:
+    """
+    Remote login not supported in Kitchen::Transport::Dummy::Connection.
+    """
+    And the exit status should not be 0
+
+  @spawn
+  Scenario: Attempting to log into a non-created instance
+    When I run `kitchen login full-flebian`
+    Then the output should contain:
+    """
+    Instance <full-flebian> has not yet been created
+    """
+    And the exit status should not be 0
+
+  @spawn
+  Scenario: Attempting to log into a non-existent instance
+    When I run `kitchen login nope`
+    Then the output should contain "No instances for regex `nope'"
+    And the exit status should not be 0
+
+  @spawn
+  Scenario: Attempting to log into an instance with an overly fuzzy match
+    When I run `kitchen login flebian`
+    Then the output should contain:
+    """
+    Argument `flebian' returned multiple results:
+      * default-flebian
+      * full-flebian
+    """
+    And the exit status should not be 0
+

data/features/kitchen_sink_command.feature

@@ -1,30 +1,30 @@
-Feature: The `kitchen sink` command
-  In order to have fun and provide an Easter Egg for users
-  As a Test Kitchen user
-  I want a `sink` command that displays ASCII art
-
-  Scenario: Displaying help
-    When I run `kitchen help`
-    Then the exit status should be 0
-    And the output should not contain "kitchen sink"
-
-  Scenario: Displaying the sink
-    When I run `kitchen sink`
-    Then the exit status should be 0
-    And the output should contain:
-      """
-                          ___
-                         ' _ '.
-                       / /` `\ \
-                       | |   [__]
-                       | |    {{
-                       | |    }}
-                    _  | |  _ {{
-        ___________<_>_| |_<_>}}________
-            .=======^=(___)=^={{====.
-           / .----------------}}---. \
-          / /                 {{    \ \
-         / /                  }}     \ \
-        (  '========================='  )
-         '-----------------------------'
-      """
+Feature: The `kitchen sink` command
+  In order to have fun and provide an Easter Egg for users
+  As a Test Kitchen user
+  I want a `sink` command that displays ASCII art
+
+  Scenario: Displaying help
+    When I run `kitchen help`
+    Then the exit status should be 0
+    And the output should not contain "kitchen sink"
+
+  Scenario: Displaying the sink
+    When I run `kitchen sink`
+    Then the exit status should be 0
+    And the output should contain:
+      """
+                          ___
+                         ' _ '.
+                       / /` `\ \
+                       | |   [__]
+                       | |    {{
+                       | |    }}
+                    _  | |  _ {{
+        ___________<_>_| |_<_>}}________
+            .=======^=(___)=^={{====.
+           / .----------------}}---. \
+          / /                 {{    \ \
+         / /                  }}     \ \
+        (  '========================='  )
+         '-----------------------------'
+      """

data/features/kitchen_test_command.feature

@@ -1,88 +1,88 @@
-Feature: Running a full test instance test
-  In order to "fire-and-forget" or run help setup a CI job
-  As an operator or CI script
-  I want to run a command that will fully test one or more instances
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    platforms:
-      - name: cool
-      - name: beans
-
-    suites:
-      - name: client
-      - name: server
-    """
-
-  @spawn
-  Scenario: Running a single instance
-    When I run `kitchen test client-beans`
-    Then the output should contain "Starting Kitchen"
-    Then the output should contain "Cleaning up any prior instances of <client-beans>"
-    Then the output should contain "Testing <client-beans>"
-    Then the output should contain "Finished testing <client-beans>"
-    Then the output should contain "Kitchen is finished."
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Running a single instance never destroying an instance
-    When I successfully run `kitchen test client-beans --destroy=never`
-    And I successfully run `kitchen list client-beans`
-    Then the output should match /^client-beans\s+.+\s+Verified$/
-
-  @spawn
-  Scenario: Running a single instance always destroying an instance
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    provisioner:
-      fail: true
-    """
-    When I run `kitchen test client-beans --destroy=always`
-    Then the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the output should match /^client-beans\s+.+\s+\<Not Created\>$/
-
-  @spawn
-  Scenario: Running a single instance not destroying an instance on failure
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    provisioner:
-      fail: true
-    """
-    When I run `kitchen test client-beans --destroy=passing`
-    Then the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the output should match /^client-beans\s+.+\s+Created$/
-
-  @spawn
-  Scenario: Running a single instance destroying an instance on success
-    When I run `kitchen test client-beans --destroy=passing`
-    Then the exit status should be 0
-    When I successfully run `kitchen list client-beans`
-    Then the output should match /^client-beans\s+.+\s+\<Not Created\>$/
-
-  @spawn
-  Scenario: Running all instances
-    When I run `kitchen test`
-    Then the output should contain "Starting Kitchen"
-    Then the output should contain "Finished testing <client-cool>"
-    Then the output should contain "Finished testing <client-beans>"
-    Then the output should contain "Finished testing <server-cool>"
-    Then the output should contain "Finished testing <server-beans>"
-    Then the output should contain "Kitchen is finished."
-    And the exit status should be 0
-    When I successfully run `kitchen list`
-    Then the output should match /^client-cool\s+.+\s+\<Not Created\>$/
-    Then the output should match /^client-beans\s+.+\s+\<Not Created\>$/
-    Then the output should match /^server-cool\s+.+\s+\<Not Created\>$/
-    Then the output should match /^server-beans\s+.+\s+\<Not Created\>$/
+Feature: Running a full test instance test
+  In order to "fire-and-forget" or run help setup a CI job
+  As an operator or CI script
+  I want to run a command that will fully test one or more instances
+
+  Background:
+    Given a file named ".kitchen.yml" with:
+    """
+    ---
+    driver:
+      name: dummy
+
+    provisioner:
+      name: dummy
+
+    platforms:
+      - name: cool
+      - name: beans
+
+    suites:
+      - name: client
+      - name: server
+    """
+
+  @spawn
+  Scenario: Running a single instance
+    When I run `kitchen test client-beans`
+    Then the output should contain "Starting Kitchen"
+    Then the output should contain "Cleaning up any prior instances of <client-beans>"
+    Then the output should contain "Testing <client-beans>"
+    Then the output should contain "Finished testing <client-beans>"
+    Then the output should contain "Kitchen is finished."
+    And the exit status should be 0
+
+  @spawn
+  Scenario: Running a single instance never destroying an instance
+    When I successfully run `kitchen test client-beans --destroy=never`
+    And I successfully run `kitchen list client-beans`
+    Then the output should match /^client-beans\s+.+\s+Verified$/
+
+  @spawn
+  Scenario: Running a single instance always destroying an instance
+    Given a file named ".kitchen.local.yml" with:
+    """
+    ---
+    provisioner:
+      fail: true
+    """
+    When I run `kitchen test client-beans --destroy=always`
+    Then the exit status should not be 0
+    When I successfully run `kitchen list client-beans`
+    Then the output should match /^client-beans\s+.+\s+\<Not Created\>$/
+
+  @spawn
+  Scenario: Running a single instance not destroying an instance on failure
+    Given a file named ".kitchen.local.yml" with:
+    """
+    ---
+    provisioner:
+      fail: true
+    """
+    When I run `kitchen test client-beans --destroy=passing`
+    Then the exit status should not be 0
+    When I successfully run `kitchen list client-beans`
+    Then the output should match /^client-beans\s+.+\s+Created$/
+
+  @spawn
+  Scenario: Running a single instance destroying an instance on success
+    When I run `kitchen test client-beans --destroy=passing`
+    Then the exit status should be 0
+    When I successfully run `kitchen list client-beans`
+    Then the output should match /^client-beans\s+.+\s+\<Not Created\>$/
+
+  @spawn
+  Scenario: Running all instances
+    When I run `kitchen test`
+    Then the output should contain "Starting Kitchen"
+    Then the output should contain "Finished testing <client-cool>"
+    Then the output should contain "Finished testing <client-beans>"
+    Then the output should contain "Finished testing <server-cool>"
+    Then the output should contain "Finished testing <server-beans>"
+    Then the output should contain "Kitchen is finished."
+    And the exit status should be 0
+    When I successfully run `kitchen list`
+    Then the output should match /^client-cool\s+.+\s+\<Not Created\>$/
+    Then the output should match /^client-beans\s+.+\s+\<Not Created\>$/
+    Then the output should match /^server-cool\s+.+\s+\<Not Created\>$/
+    Then the output should match /^server-beans\s+.+\s+\<Not Created\>$/