test-kitchen 1.23.3 → 1.23.4

data/features/kitchen_help_command.feature

@@ -1,16 +0,0 @@
-Feature: Using Test Kitchen CLI help
-  In order to access the self describing documentation
-  As a user of Test Kitchen
-  I want to run a command help help for kitchen commands
-
-  @spawn
-  Scenario: Printing help
-    When I run `kitchen help`
-    Then the exit status should be 0
-    And the output should contain "kitchen help [COMMAND]"
-
-  @spawn
-  Scenario: Bad arugments should exit nonzero
-    When I run `kitchen help -d always -c`
-    Then the exit status should not be 0
-    And the output should contain "Usage: "

data/features/kitchen_init_command.feature

@@ -1,254 +0,0 @@
-Feature: Add Test Kitchen support to an existing project
-  In order to add Test Kitchen to a project with minimal effort
-  As an operator
-  I want to run a command to initialize my project
-
-  @spawn
-  Scenario: Displaying help
-    When I run `kitchen help init`
-    Then the output should contain:
-    """
-    Usage:
-      kitchen init
-    """
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Running init with default values
-    Given I have a git repository
-    When I run `kitchen init`
-    Then the exit status should be 0
-    And a directory named "test/integration/default" should exist
-    And the file ".gitignore" should contain ".kitchen/"
-    And the file ".gitignore" should contain "kitchen.local.yml"
-    And the file ".gitignore" should contain ".kitchen.local.yml"
-    And the file "kitchen.yml" should exist:
-    And the file "kitchen.yml" should contain:
-    """
-    driver:
-      name: vagrant
-    """
-    And a file named "Gemfile" should not exist
-    And a file named "Rakefile" should not exist
-    And a file named "Thorfile" should not exist
-    And a gem named "kitchen-vagrant" is installed
-    And a file named "chefignore" should exist
-    And the file "chefignore" should contain ".kitchen"
-
-  Scenario: Running init that creates a Gemfile
-    When I successfully run `kitchen init --create-gemfile`
-    Then the file "Gemfile" should contain "https://rubygems.org"
-    And the file "Gemfile" should contain:
-    """
-    gem "test-kitchen"
-    """
-    And the output should contain "You must run `bundle install'"
-
-  Scenario: Running init with an existing Gemfile appends to the Gemfile
-    Given a file named "Gemfile" with:
-    """
-    source "https://rubygems.org"
-
-
-    """
-    When I successfully run `kitchen init`
-    Then the file "Gemfile" should contain exactly:
-    """
-    source "https://rubygems.org"
-
-    gem "test-kitchen"
-
-    """
-    And the output should contain "You must run `bundle install'"
-
-  Scenario: Running init with a Gemfile containing test-kitchen does not
-    re-append
-    Given a file named "Gemfile" with:
-    """
-    source "https://rubygems.org"
-
-    gem 'test-kitchen'
-
-    """
-    When I successfully run `kitchen init`
-    Then the file "Gemfile" should contain exactly:
-    """
-    source "https://rubygems.org"
-
-    gem 'test-kitchen'
-
-    """
-
-  Scenario: Running init with a Gemfile containing the driver gem does not
-    re-append
-    Given a file named "Gemfile" with:
-    """
-    source "https://rubygems.org"
-
-    gem 'test-kitchen'
-    gem 'kitchen-ec2'
-
-    """
-    When I successfully run `kitchen init --driver=kitchen-ec2`
-    Then the file "Gemfile" should contain exactly:
-    """
-    source "https://rubygems.org"
-
-    gem 'test-kitchen'
-    gem 'kitchen-ec2'
-
-    """
-    And the output should not contain "You must run `bundle install'"
-
-  Scenario: Running init with multiple driver sets the plugin_driver to the
-    first driver given
-    Given an empty file named "Gemfile"
-    When I successfully run `kitchen init --driver=kitchen-bluebox kitchen-wakka`
-    Then the file "kitchen.yml" should exist
-    Then the file "kitchen.yml" should contain:
-    """
-    driver:
-      name: bluebox
-    """
-
-  Scenario: Running init with no drivers sets the plugin_driver to the
-    dummy driver
-    Given an empty file named "Gemfile"
-    When I successfully run `kitchen init --no-driver`
-    Then the file "kitchen.yml" should contain:
-    """
-    driver:
-      name: dummy
-    """
-
-  Scenario: Running init without a provisioner sets the default provisioner
-    to chef_solo in kitchen.yml
-    Given an empty file named "Gemfile"
-    When I successfully run `kitchen init --no-driver`
-    Then the file "kitchen.yml" should contain:
-    """
-    provisioner:
-      name: chef_solo
-    """
-
-  Scenario: Running init with a provisioner sets the provisioner in kitchen.yml
-    Given an empty file named "Gemfile"
-    When I successfully run `kitchen init --no-driver --provisioner=chef_zero`
-    Then the file "kitchen.yml" should contain:
-    """
-    provisioner:
-      name: chef_zero
-    """
-
-  Scenario: Running with a Rakefile file appends Kitchen tasks
-    Given an empty file named "Gemfile"
-    And an empty file named "Rakefile"
-    When I successfully run `kitchen init`
-    Then the file "Rakefile" should contain:
-    """
-    begin
-      require 'kitchen/rake_tasks'
-      Kitchen::RakeTasks.new
-    rescue LoadError
-      puts '>>>>> Kitchen gem not loaded, omitting tasks' unless ENV['CI']
-    end
-    """
-
-  Scenario: Running without git doesn't make a .gitignore
-    When I successfully run `kitchen init --no-driver`
-    Then the exit status should be 0
-    And a file named ".gitignore" should not exist
-
-  Scenario: Running with a Thorfile file appends Kitchen tasks
-    Given an empty file named "Gemfile"
-    Given an empty file named "Thorfile"
-    When I successfully run `kitchen init`
-    Then the file "Thorfile" should contain:
-    """
-    begin
-      require 'kitchen/thor_tasks'
-      Kitchen::ThorTasks.new
-    rescue LoadError
-      puts '>>>>> Kitchen gem not loaded, omitting tasks' unless ENV['CI']
-    end
-    """
-
-  Scenario: Running init with a name in metadata.rb sets a run list
-    Given an empty file named "Gemfile"
-    Given a file named "metadata.rb" with:
-    """
-    name              "ntp"
-    license           "Apache 2.0"
-    description       "Installs and configures ntp as a client or server"
-    version           "0.1.0"
-
-    support "ubuntu"
-    support "centos"
-    """
-    When I successfully run `kitchen init`
-    Then the file "kitchen.yml" should contain exactly:
-    """
-    ---
-    driver:
-      name: vagrant
-
-    provisioner:
-      name: chef_solo
-
-    platforms:
-      - name: ubuntu-16.04
-      - name: centos-7
-
-    suites:
-      - name: default
-        run_list:
-          - recipe[ntp::default]
-        attributes:
-
-    """
-
-  Scenario: Running init with an empty file metadata.rb sets an empty run list
-    Given an empty file named "metadata.rb"
-    When I successfully run `kitchen init`
-    Then the file "kitchen.yml" should contain exactly:
-    """
-    ---
-    driver:
-      name: vagrant
-
-    provisioner:
-      name: chef_solo
-
-    platforms:
-      - name: ubuntu-16.04
-      - name: centos-7
-
-    suites:
-      - name: default
-        run_list:
-        attributes:
-
-    """
-
-  Scenario: Running init with no metadata.rb file sets an empty run list
-    Given a file named "metadata.rb" does not exist
-    When I successfully run `kitchen init`
-    Then the file "kitchen.yml" should contain exactly:
-    """
-    ---
-    driver:
-      name: vagrant
-
-    provisioner:
-      name: chef_solo
-
-    platforms:
-      - name: ubuntu-16.04
-      - name: centos-7
-
-    suites:
-      - name: default
-        run_list:
-        attributes:
-
-    """

data/features/kitchen_list_command.feature

@@ -1,140 +0,0 @@
-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\>\s+\<None\>$/
-    And the output should match /^foobar-centos-64\s+Dummy\s+ChefSolo\s+Busser\s+Ssh\s+\<Not Created\>\s+\<None\>$/
-
-  Scenario: Listing a single instance with the --json option
-    When I run `kitchen list --json`
-    Then the exit status should be 0
-    And the output should contain exactly:
-    """
-    [
-      {
-        "instance": "foobar-ubuntu-1304",
-        "driver": "Dummy",
-        "provisioner": "ChefSolo",
-        "verifier": "Busser",
-        "transport": "Ssh",
-        "last_action": null,
-        "last_error": null
-      },
-      {
-        "instance": "foobar-centos-64",
-        "driver": "Dummy",
-        "provisioner": "ChefSolo",
-        "verifier": "Busser",
-        "transport": "Ssh",
-        "last_action": null,
-        "last_error": null
-      },
-      {
-        "instance": "foobar-centos-64-with-small-mem",
-        "driver": "Dummy",
-        "provisioner": "ChefSolo",
-        "verifier": "Busser",
-        "transport": "Ssh",
-        "last_action": null,
-        "last_error": null
-      }
-    ]
-    """
-
-  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-16.04
-
-    suites:
-      - name: gdb01-master
-      - name: logdb01-master
-    """
-    When I successfully run `kitchen list gdb01-master-ubuntu-1604 --bare`
-    Then the output should contain exactly:
-    """
-    gdb01-master-ubuntu-1604
-
-    """
-
-  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 +0,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
-