Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Test Kitchen

kitchen.ci

  • Free plan
  • Open source
  • Windows
  • macOS
  • Linux
  • API
  • Self-hosted
8.1 Club score Visit kitchen.ci

What Test Kitchen is

Test Kitchen is a free test harness for running infrastructure code in isolation on one or more platforms. Its workflow uses create, converge, setup, verify, and destroy commands to provision environments and check the code. Documented drivers target Amazon EC2, Apache CloudStack, DigitalOcean, Docker through Dokken, Google Cloud Platform, Hetzner Cloud, Vagrant, Azure, Hyper-V, OpenStack, VMware vCenter, and VMware vRealize Automation. Driver availability depends on which driver gems are installed in the Ruby environment running Kitchen. Provisioners can configure instances with Chef Infra, Cinc Client, Habitat, PowerShell DSC, or shell scripts, and listed verification integrations include Cinc Auditor, Chef InSpec, and Serverspec. Community-maintained plugins add Ansible, Puppet, and Salt provisioners. Test Kitchen can be installed from RubyGems, system packages, or Cinc Workstation, but it does not bundle Cinc or Chef tooling itself. The stated prerequisites are a 64-bit operating system and enabled CPU virtualization. It is licensed under Apache License 2.0, and the documentation directs users to Chef Community Slack for community assistance. The documentation says kitchen-docker has known issues and no current maintainer, and recommends kitchen-dokken instead.

Who it suits

Test Kitchen may suit infrastructure developers using a test-driven workflow to build and test Chef Infra cookbooks. Its provisioner and verifier options also cover several other infrastructure testing setups.

Good to know, and what to watch

  • Free and licensed under Apache License 2.0.
  • Workflow includes create, converge, verify, and destroy.
  • Supports multiple documented infrastructure drivers.
  • Listed verifiers include Cinc Auditor, InSpec, and Serverspec.
  • Community plugins add Ansible, Puppet, and Salt.
  • Requires a 64-bit operating system.
  • CPU virtualization must be enabled.
  • Available drivers depend on installed driver gems.
  • kitchen-docker has known issues and no current maintainer.

Open-source Test Kitchen

Free

Free plan

Getting started

  1. Install Test Kitchen with gem install test-kitchen, a system package, or Cinc Workstation
  2. Use a 64-bit operating system with CPU virtualization enabled
  3. Install the driver gems for the platforms you plan to target
  4. Choose provisioners and verifiers for the infrastructure workflow
  5. Run create, converge, setup, verify, and destroy commands

The Club's review

Overview

Test Kitchen is an open-source harness for running infrastructure tests against isolated platforms, best suited to practitioners who want a repeatable command-line workflow for infrastructure changes. Its flexibility across drivers and provisioners is the main draw; the trade-off is that users must manage Ruby tooling, driver gems, and the environment prerequisites.

It makes the most sense for teams building and checking infrastructure code, especially Chef Infra cookbooks, rather than anyone seeking a bundled graphical testing service. For a wider view of tools in this category, see the Infrastructure Testing Tools list.

Key features

The workflow proceeds through create, converge, setup, verify, and destroy: provision a platform, apply the infrastructure code, prepare and check the instance, then tear it down. That sequence gives development teams a clear structure for repeatable checks, including test-driven development. It is useful coordination rather than an all-in-one environment, so users remain responsible for selecting and installing the pieces they need.

Documented drivers cover Amazon EC2, Apache CloudStack, DigitalOcean, Docker through Dokken, Google Cloud Platform, Hetzner Cloud, Vagrant, Azure, Hyper-V, OpenStack, VMware vCenter, and VMware vRealize Automation. This range helps teams target different environments, but a driver is available only when its gem is installed in Kitchen’s Ruby environment.

Provisioning options include Chef Infra, Cinc Client, Habitat, PowerShell DSC, and shell scripts. Community-maintained plugins add Ansible, Puppet, and Salt. The home page identifies Cinc Auditor, Chef InSpec, and Serverspec as testing-framework integrations. Together, these choices make Kitchen relevant beyond Chef, though users need to assemble the provisioners and verifiers their workflow requires.

Installation is available through RubyGems, system packages, or Cinc Workstation; the RubyGems command is gem install test-kitchen. Kitchen itself does not include Cinc or Chef tooling. Workstation packages bundle drivers, provisioners, verifiers, and commands, so the chosen installation route affects how much setup users must handle.

One important caveat: the kitchen-docker driver lacks a maintainer and has known issues. The documentation recommends kitchen-dokken instead, making Dokken the more sensible choice for users who want a Docker-based driver.

Pricing

Open-source Test Kitchen costs free under the Apache License 2.0. There are no paid tiers or seat-based distinctions in this plan. The zero price does not remove the setup work: users still need an appropriate Ruby environment, installed driver gems, and the required platform prerequisites.

Platforms

Test Kitchen supports Linux, macOS, and Windows. Its getting-started guide requires a 64-bit operating system and enabled CPU virtualization. The execution model is local, while documented drivers reach cloud and virtualization platforms including Amazon EC2, Microsoft Azure, Google Compute Engine, DigitalOcean, OpenStack, and others. Actual driver availability depends on the installed gems.

Who it's for

Kitchen is a good fit for infrastructure developers who want to provision isolated environments and verify changes in a structured workflow, particularly those working with Chef Infra cookbooks. Ansible, PowerShell DSC, Puppet, and Salt users can also use its provisioner options. It is a weaker fit for newcomers who want a ready-made service: the Ruby environment, virtualization prerequisites, and driver dependencies demand some technical setup.

Pros and cons

  • Pros: A consistent five-command lifecycle makes infrastructure checks repeatable and includes teardown as part of the workflow.
  • Pros: A broad set of documented drivers and multiple provisioner and verifier choices can accommodate varied infrastructure stacks.
  • Pros: The Apache-licensed open-source plan is free, with installation options ranging from RubyGems to bundled Workstation packages.
  • Cons: Drivers depend on Ruby gems installed in the running environment, so platform support requires configuration rather than coming automatically.
  • Cons: The 64-bit operating system and CPU virtualization prerequisites may rule out or complicate some local setups.
  • Cons: The kitchen-docker driver has known issues and no maintainer; users should prefer kitchen-dokken for Docker workflows.

Alternatives

Chef InSpec is worth considering when compliance checks are the priority: it has a free plan for unlimited duration, but that plan is limited to non-production workloads and personal, non-commercial use.

Conftest is another free, Apache-licensed option on Linux, macOS, and Windows.

kube-score is a free, MIT-licensed tool available across Linux, macOS, Windows, web, and self-hosted platforms.

kubeconform is a free alternative for Linux, macOS, Windows, and self-hosted environments, with no paid plans or usage limits stated on its official site.

Terratest is a free, Apache 2.0-licensed open-source project built by Gruntwork; its listed platform is Linux.

CloudSploit offers a free, self-hosted open-source version as well as a commercial hosted version at custom pricing.

AWS CloudFormation is a free service for CloudFormation itself, though underlying AWS resources are billed at their own rates.

cfn-lint is a free, MIT-0-licensed option for Linux, macOS, Windows, and self-hosted environments, with Python 3.10–3.14 support.

Verdict

Choose Test Kitchen if you need a free, adaptable way to provision isolated platforms and check infrastructure code through a repeatable lifecycle. Its combination of drivers and provisioner integrations is compelling for infrastructure teams, but the Ruby-gem dependencies and local virtualization requirements make it less suitable for users who want a turnkey testing service.

The verdict

Test Kitchen provides a command-based workflow for provisioning and checking infrastructure code across documented platforms. Check its prerequisites and driver-gem requirements, and note the documentation’s recommendation to use kitchen-dokken instead of kitchen-docker.

Questions people ask

What does Test Kitchen cost?

The Open-source Test Kitchen plan is free at no cost under Apache License 2.0.

Which operating systems can run Test Kitchen?

It is available on Linux, macOS, and Windows. The getting-started guide requires a 64-bit operating system.

Which infrastructure tools does it support?

Listed support includes Chef Infra cookbooks, Ansible, PowerShell DSC, Puppet, and Salt.

Can it test cloud environments?

Documented drivers target services and platforms including Amazon EC2, Microsoft Azure, Google Cloud Platform, DigitalOcean, OpenStack, and VMware products.

How can users get help?

The documentation directs users to the #test-kitchen channel on Chef Community Slack.

What the maker publishes

Additional provisioners
The documentation lists community-maintained kitchen-ansible, kitchen-puppet, and kitchen-salt plugins. source
Audience
The getting-started guide demonstrates using Test Kitchen to create and test a Chef Infra cookbook and describes a test-driven development workflow. source
Built-in workflows
The documented lifecycle uses create, converge, setup, verify, and destroy commands. source
Chef dependency handling
Chef workflows can resolve cookbook dependencies through Berkshelf or Policyfiles, or use a cookbooks directory. source
Company founded
Progress says four founders created the company in 1981. source
Company headquarters
LinkedIn identifies Burlington, Massachusetts as Progress Software headquarters. source
Company size
LinkedIn lists Progress Software as a public software-development company with 1,001–5,000 employees and 4,302 discoverable employees. source
Current release
GitHub lists Test Kitchen 4.1.5, released on September 18, 2026, with streamed log formatter reuse as a performance improvement. source
Documentation depth
The documentation site contains getting-started guides, command references, driver, transport, provisioner and verifier pages, configuration reference, contracts, examples, FAQ, lifecycle hooks, and glossary. source
Driver architecture
Drivers connect Test Kitchen to virtualization systems and cloud providers including Vagrant, Amazon EC2, Azure, Google Compute Engine, VMware, and Docker. source
Driver availability
Driver availability depends on which driver gems are installed in the Ruby environment running Kitchen. source
Driver integrations
Official driver documentation covers AWS EC2, CloudStack, DigitalOcean, Docker via Dokken, Google Cloud, Hetzner, Vagrant, Azure, Hyper-V, OpenStack, VMware vCenter, and VMware vRealize Automation. source
Drivers
Documented drivers target Amazon EC2, Apache CloudStack, DigitalOcean, Docker via Dokken, Google Cloud Platform, Hetzner Cloud, Vagrant, Azure, Hyper-V, OpenStack, VMware vCenter, and VMware vRealize Automation. source
Extensibility API
The current driver contract documents the existing driver API behavior and implementation details for plugin authors. source
Installation
Test Kitchen can be installed from RubyGems, system packages, or Cinc Workstation; the documented RubyGems command is gem install test-kitchen. source
Installation
Users can install the gem with gem install test-kitchen or install Cinc Workstation. source
License
The site identifies Test Kitchen as Apache License, Version 2.0. source
License
The project is released under the Apache License 2.0. source
Limit: abstraction overhead
A G2 reviewer wanted the underlying Vagrant configuration exposed verbatim instead of abstracted behind Kitchen configuration. source
Limitations
The documentation says the kitchen-docker driver is currently without a maintainer and has known issues, and recommends kitchen-dokken instead. source
Limit: information discoverability
A G2 reviewer said some recipe information was complicated to reach and look up. source
Limit: learning curve
A G2 reviewer said users need substantial DevOps knowledge and can spend hours resolving minor cookbook bugs. source
Limit: legacy driver projects
The documentation marks kitchen-rackspace as unmaintained and says several other historical drivers are not listed because they are unmaintained or superseded. source
Limit: plugin availability
Available drivers depend on which gems are installed in the particular Ruby, Cinc Workstation, or Chef Workstation environment. source

Checked against the maker's pages on 15 Oct 2026.