• Getting Started
    • Introduction
    • Installing
    • Getting Help
    • Creating a Cookbook
    • kitchen.yml
    • Instances
    • Writing a Recipe
    • kitchen converge
    • Manually Verifying
    • Writing a Test
    • kitchen verify
    • kitchen test
    • Adding a Platform
    • Adding a New Feature
    • Adding a Suite
    • Adding a Test
    • Adding a Recipe
    • Excluding Platforms
    • Next Steps
  • Drivers
    • About Drivers
    • Amazon AWS (EC2)
    • DigitalOcean
    • Dokken (Docker)
    • Google Cloud Platform
    • HashiCorp Vagrant
    • Microsoft Azure
    • Microsoft Hyper-V
    • OpenStack
    • VMware vCenter
    • VMware vRealize Automation
  • Transports
    • About Transports
    • SSH
    • WinRM
  • Provisioners
    • About Provisioners
    • Chef Infra
    • Shell
  • Verifiers
    • Verifiers
    • InSpec
    • ServerSpec
  • Reference
    • Configuration
    • Examples
    • FAQ
    • Current Driver Contract
    • Fixture Cookbooks
    • Current Transport Contract
    • Current Provisioner Contract
    • Current Verifier Contract
    • Glossary
    • Lifecycle Hooks
    • Reboots

Verifiers

A Test Kitchen verifier tests the configuration applied by the provisioner. The test-kitchen gem includes the legacy busser verifier and the built-in shell verifier. InSpec, Cinc Auditor, ServerSpec, Pester, and BATS support is supplied by plugin gems installed in the Ruby environment that runs kitchen.

Common verifier plugins:

  • kitchen-inspec
  • kitchen-cinc-auditor
  • busser-bats
  • busser-serverspec
  • kitchen-pester
  • Licensing
  • Terms & Conditions
  • Trademark Policy
  • Privacy Policy

Apache License, Version 2.0 (see LICENSE)