Test Kitchen
kitchen.ci
What it 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 test infrastructure code. Documented drivers cover Amazon EC2, Apache CloudStack, DigitalOcean, Docker through Dokken, Google Cloud Platform, Hetzner Cloud, Vagrant, Azure, Hyper-V, OpenStack, and VMware products. Which drivers are available depends on the driver gems installed in the Ruby environment. Provisioning options include Chef Infra, Cinc Client, Habitat, PowerShell DSC, and shell scripts; listed verification integrations include Cinc Auditor, Chef InSpec, and Serverspec. Community plugins add Ansible, Puppet, and Salt provisioners. Installation is available through RubyGems, system packages, or Cinc Workstation, but Test Kitchen itself does not bundle Cinc or Chef tooling. Requirements include a 64-bit operating system and enabled CPU virtualization. The project uses Apache License 2.0 and points users to Chef Community Slack for community assistance. The documentation notes known issues and no current maintainer for kitchen-docker, recommending kitchen-dokken instead.
Spec sheet
- What it does
- Test Kitchen runs infrastructure code against one or more isolated target platforms.Read 15 Oct 2026 · kitchen.ci
- Purpose
- Test Kitchen is a test harness for executing infrastructure code on one or more platforms in isolation.Read 30 Sep 2026 · kitchen.ci
- Audience
- The getting-started guide demonstrates using Test Kitchen to create and test a Chef Infra cookbook and describes a test-driven development workflow.Read 30 Sep 2026 · kitchen.ci
- Support
- The documentation directs users to the #test-kitchen channel on Chef Community Slack for assistance from community members.Read 30 Sep 2026 · kitchen.ci
- License
- The project is released under the Apache License 2.0.Read 15 Oct 2026 · kitchen.ci
- Additional provisioners
- The documentation lists community-maintained kitchen-ansible, kitchen-puppet, and kitchen-salt plugins.Read 30 Sep 2026 · kitchen.ci
- Built-in workflows
- The documented lifecycle uses create, converge, setup, verify, and destroy commands.Read 15 Oct 2026 · kitchen.ci
- Chef dependency handling
- Chef workflows can resolve cookbook dependencies through Berkshelf or Policyfiles, or use a cookbooks directory.Read 15 Oct 2026 · kitchen.ci
- Company founded
- Progress says four founders created the company in 1981.Read 15 Oct 2026 · progress.com
- Company headquarters
- LinkedIn identifies Burlington, Massachusetts as Progress Software headquarters.Read 15 Oct 2026 · linkedin.com
- Company size
- LinkedIn lists Progress Software as a public software-development company with 1,001–5,000 employees and 4,302 discoverable employees.Read 15 Oct 2026 · linkedin.com
- Current release
- GitHub lists Test Kitchen 4.1.5, released on September 18, 2026, with streamed log formatter reuse as a performance improvement.Read 15 Oct 2026 · github.com
- 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.Read 15 Oct 2026 · kitchen.ci
- Driver architecture
- Drivers connect Test Kitchen to virtualization systems and cloud providers including Vagrant, Amazon EC2, Azure, Google Compute Engine, VMware, and Docker.Read 15 Oct 2026 · kitchen.ci
- Driver availability
- Driver availability depends on which driver gems are installed in the Ruby environment running Kitchen.Read 30 Sep 2026 · kitchen.ci
- 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.Read 15 Oct 2026 · kitchen.ci
- 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.Read 30 Sep 2026 · kitchen.ci
- Extensibility API
- The current driver contract documents the existing driver API behavior and implementation details for plugin authors.Read 15 Oct 2026 · kitchen.ci
- Installation
- Users can install the gem with gem install test-kitchen or install Cinc Workstation.Read 15 Oct 2026 · kitchen.ci
- Limit: abstraction overhead
- A G2 reviewer wanted the underlying Vagrant configuration exposed verbatim instead of abstracted behind Kitchen configuration.Read 15 Oct 2026 · g2.com
- Limit: information discoverability
- A G2 reviewer said some recipe information was complicated to reach and look up.Read 15 Oct 2026 · g2.com
- Limit: learning curve
- A G2 reviewer said users need substantial DevOps knowledge and can spend hours resolving minor cookbook bugs.Read 15 Oct 2026 · g2.com
- 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.Read 15 Oct 2026 · kitchen.ci
- Limit: plugin availability
- Available drivers depend on which gems are installed in the particular Ruby, Cinc Workstation, or Chef Workstation environment.Read 15 Oct 2026 · kitchen.ci
- Limit: unmaintained Docker driver
- The driver documentation says kitchen-docker is currently without a maintainer and has known issues, recommending kitchen-dokken instead.Read 15 Oct 2026 · kitchen.ci
- Limitations
- The documentation says the kitchen-docker driver is currently without a maintainer and has known issues, and recommends kitchen-dokken instead.Read 30 Sep 2026 · kitchen.ci
- Owner acquisition
- Progress Software completed its acquisition of Chef Software on October 5, 2020, for approximately $220 million in cash.Read 15 Oct 2026 · sec.gov
- Plugin ecosystem
- Drivers, provisioners, transports, and verifiers are supplied through Ruby gems installed in the Ruby environment running kitchen.Read 15 Oct 2026 · kitchen.ci
- Praise: bug reduction
- A G2 reviewer said Test Kitchen catches bugs before code reaches the team test environment.Read 15 Oct 2026 · g2.com
- Praise: cloud integration
- A G2 reviewer praised Chef continuous deployment and its fit with cloud infrastructure.Read 15 Oct 2026 · g2.com
- Praise: local multi-platform testing
- A G2 reviewer praised provisioning multiple temporary Vagrant machines to test cookbooks across platforms and scenarios.Read 15 Oct 2026 · g2.com
- Prerequisites
- The getting-started guide lists a 64-bit operating system and enabled CPU virtualization as prerequisites.Read 30 Sep 2026 · kitchen.ci
- Provisioners
- Documented provisioners include Chef Infra, Cinc Client, Habitat, PowerShell DSC, and shell scripts.Read 15 Oct 2026 · kitchen.ci
- Rating on G2
- 4.7 out of 5 from 5 reviewsRead 15 Oct 2026 · g2.com
- Recent breaking change
- Version 4.0.0 removed Chef provisioners from the core and changed the default provisioner to shell.Read 15 Oct 2026 · github.com
- Review-site pricing
- G2 states that pricing details are not currently available for Test Kitchen.Read 15 Oct 2026 · g2.com
- Security or compliance claims
- The reviewed official pages provide no specific security certification or compliance claim for Test Kitchen.Read 15 Oct 2026 · kitchen.ci
- Self-hosting model
- Test Kitchen runs locally or in a user-controlled Ruby environment and is installed as a gem or workstation component.Read 15 Oct 2026 · kitchen.ci
- Supported test frameworks
- The home page lists Cinc Auditor, Chef InSpec, and Serverspec as supported testing frameworks.Read 15 Oct 2026 · kitchen.ci
- System requirements
- The installation guide requires a 64-bit operating system, hardware virtualization enabled, and a processor supporting Intel VT-x or AMD-V.Read 15 Oct 2026 · kitchen.ci
- Verifier integrations
- Documented verifiers include InSpec, Cinc Auditor, Pester, and ServerSpec, with additional BATS, RSpec, and Minitest plugins listed.Read 15 Oct 2026 · kitchen.ci
- Windows limitation
- The installation guide says Hyper-V must be disabled as a Windows feature for VirtualBox to function because the hypervisors conflict.Read 15 Oct 2026 · kitchen.ci
- Workflow
- Its basic workflow uses create, converge, setup, verify, and destroy commands to provision platforms and test infrastructure code.Read 30 Sep 2026 · kitchen.ci
- Workstation dependencies
- Test Kitchen itself does not bundle Cinc or Chef tooling, and Workstation packages provide the drivers, provisioners, verifiers, and commands bundled in that package.Read 30 Sep 2026 · kitchen.ci
Plans and prices
Open-source Test Kitchen Free Apache License 2.0 · self-managed Ruby installation Read 15 Oct 2026 · kitchen.ci
Strong points and limits
Strong points
- Free under Apache License 2.0
- Supports multiple infrastructure provisioning methods
- Offers several verification integrations
- Installable through RubyGems, system packages, or Workstation
- Works across one or more isolated platforms
Limits
- Requires a 64-bit operating system and CPU virtualization
- Available drivers depend on installed Ruby gems
- Test Kitchen does not bundle Cinc or Chef tooling
- kitchen-docker has known issues and no maintainer
Who it suits
It suits infrastructure developers using a test-driven workflow, including those testing Chef Infra cookbooks. Its drivers and provisioners cover several cloud, virtualization, and configuration-management options.
Verdict
Test Kitchen provides a command-based workflow for provisioning and checking infrastructure code across varied platforms. Check runtime prerequisites and installed driver gems, and consider the documented recommendation to use kitchen-dokken rather than kitchen-docker.
Where Specifiction places it
- Infrastructure Testing Tools#7 of 288.2
Alternatives to Test KitchenAll alternatives →
CIS-CAT Pro Assessor From $200/mo · Free plan 9.3 Visit 
AWS CloudFormation Free plan 9.1 Visit