Skip to main content

Test Kitchen drivers

A Test Kitchen driver configures the compute instance that Test Kitchen uses for isolated cookbook testing. A driver targets a local hypervisor, a hypervisor abstraction layer such as Vagrant, or a cloud service such as Amazon EC2.

Note

Chef Workstation includes many common Test Kitchen drivers.

Most drivers have driver-specific settings that you add to the kitchen.yml file before Test Kitchen can use that platform. Driver availability depends on the Ruby environment that runs kitchen. To confirm that a driver is available, list its gem before you rely on it:

# System Ruby
gem list kitchen-vagrant

# Chef Workstation
chef gem list kitchen-vagrant

If a driver isn’t installed, add its gem to that same environment.

Supported drivers

The following drivers have dedicated configuration pages:

  • kitchen-azurerm: Provisions virtual machines on Microsoft Azure.
  • kitchen-digitalocean: Provisions droplets on DigitalOcean. This driver ships with Chef Workstation.
  • kitchen-dokken: Runs fast cookbook tests using Docker. This driver ships with Chef Workstation.
  • kitchen-ec2: Provisions instances on Amazon EC2. This driver ships with Chef Workstation.
  • kitchen-google: Provisions instances on Google Compute Engine. This driver ships with Chef Workstation.
  • kitchen-hyperv: Provisions virtual machines on Microsoft Hyper-V. This driver ships with Chef Workstation.
  • kitchen-openstack: Provisions instances on OpenStack. This driver ships with Chef Workstation.
  • kitchen-vagrant: Provisions local virtual machines with HashiCorp Vagrant. This driver ships with Chef Workstation.
  • kitchen-vcenter: Provisions virtual machines on VMware vCenter.
  • kitchen-vra: Provisions machines through VMware vRealize Automation.

Additional drivers

The following drivers are also available. For configuration details, see each driver’s repository:

For the full list of maintained drivers, see the Test Kitchen drivers reference.

Thank you for your feedback!

×