Contents

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

    platforms:
      - name: cool
      - name: beans

    suites:
      - name: client
      - name: server
    """

  @spawn
  Scenario: Showing all instances
    When I run `kitchen diagnose`
    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: 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 exit status should be 0

Version data entries

4 entries across 4 versions & 1 rubygems

Version	Path
test-kitchen-1.4.0.beta.2	features/kitchen_diagnose_command.feature
test-kitchen-1.4.0.beta.1	features/kitchen_diagnose_command.feature
test-kitchen-1.3.1	features/kitchen_diagnose_command.feature
test-kitchen-1.3.0	features/kitchen_diagnose_command.feature