Freedom251 › Infrastructure Testing Tools
Test Kitchen
What Test Kitchen is
Test Kitchen is a free test harness for running infrastructure code in isolation across one or more platforms. Its workflow moves through create, converge, setup, verify, and destroy commands to provision environments and check the 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 can use Chef Infra, Cinc Client, Habitat, PowerShell DSC, or shell scripts; listed verification integrations include Cinc Auditor, Chef InSpec, and Serverspec. Community plugins add Ansible, Puppet, and Salt options. It runs on Linux, macOS, and Windows, and can be installed from RubyGems, system packages, or Cinc Workstation. It requires a 64-bit operating system and enabled CPU virtualization. Test Kitchen is licensed under Apache License 2.0. The kitchen-docker driver has known issues and no current maintainer; the documentation recommends kitchen-dokken instead.
Who it suits
Test Kitchen suits infrastructure teams that want to create and test infrastructure code across isolated platforms, especially teams working with Chef Infra cookbooks or the supported provisioning and verification tools.
What it does well
- Free and licensed under Apache License 2.0.
- Supports Linux, macOS, and Windows.
- Offers a broad range of documented drivers.
- Supports several provisioners and verifier integrations.
What to know first
- Requires a 64-bit OS and enabled CPU virtualization.
- Available drivers depend on installed Ruby gems.
- The kitchen-docker driver has known issues and no maintainer.
Limits
The free plan is open-source software under Apache License 2.0. Driver availability depends on installed Ruby gems; Test Kitchen itself does not bundle Cinc or Chef tooling. The kitchen-docker driver has known issues and no current maintainer.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Open-source Test Kitchen | Apache License 2.0 · self-managed Ruby installation | Free |
As kitchen.ci lists them, read 15 Oct 2026. The maker's own page has the final word.
Getting started
- Choose an installation route: RubyGems, system packages, or Cinc Workstation.
- For RubyGems, run `gem install test-kitchen`.
- Confirm the system is 64-bit and CPU virtualization is enabled.
- Install the driver gems needed for the environments you plan to use.
- Choose a provisioner and verification framework, then use the create, converge, setup, verify, and destroy workflow.
Verdict
Test Kitchen provides a command-based workflow for provisioning platforms and verifying infrastructure code. Check the driver and tooling requirements for your Ruby environment before choosing an installation path.
Questions
How much does Test Kitchen cost?
The listed Open-source Test Kitchen plan is free.
What operating systems does it support?
The listed platforms are Linux, macOS, and Windows. Its getting-started guide also requires a 64-bit operating system and enabled CPU virtualization.
Is Test Kitchen open source?
Yes. The site identifies it as licensed under Apache License, Version 2.0.
How can I install it?
It can be installed from RubyGems, system packages, or Cinc Workstation. The documented RubyGems command is `gem install test-kitchen`.
Which infrastructure tools can it provision?
Documented provisioners include Chef Infra, Cinc Client, Habitat, PowerShell DSC, and shell scripts. Community-maintained plugins add Ansible, Puppet, and Salt.
Does it include Chef tooling?
Test Kitchen does not bundle Cinc or Chef tooling. Workstation packages provide the drivers, provisioners, verifiers, and commands included in each package.
Facts from Test Kitchen's own pages
- Additional provisioners
- The documentation lists community-maintained kitchen-ansible, kitchen-puppet, and kitchen-salt plugins. · kitchen.ci, 30 Sept 2026
- Audience
- The getting-started guide demonstrates using Test Kitchen to create and test a Chef Infra cookbook and describes a test-driven development workflow. · kitchen.ci, 30 Sept 2026
- Built-in workflows
- The documented lifecycle uses create, converge, setup, verify, and destroy commands. · kitchen.ci, 15 Oct 2026
- Chef dependency handling
- Chef workflows can resolve cookbook dependencies through Berkshelf or Policyfiles, or use a cookbooks directory. · kitchen.ci, 15 Oct 2026
- Company founded
- Progress says four founders created the company in 1981. · progress.com, 15 Oct 2026
- Company headquarters
- LinkedIn identifies Burlington, Massachusetts as Progress Software headquarters. · linkedin.com, 15 Oct 2026
- Company size
- LinkedIn lists Progress Software as a public software-development company with 1,001–5,000 employees and 4,302 discoverable employees. · linkedin.com, 15 Oct 2026
- Current release
- GitHub lists Test Kitchen 4.1.5, released on September 18, 2026, with streamed log formatter reuse as a performance improvement. · github.com, 15 Oct 2026
- 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. · kitchen.ci, 15 Oct 2026
- Driver architecture
- Drivers connect Test Kitchen to virtualization systems and cloud providers including Vagrant, Amazon EC2, Azure, Google Compute Engine, VMware, and Docker. · kitchen.ci, 15 Oct 2026
- Driver availability
- Driver availability depends on which driver gems are installed in the Ruby environment running Kitchen. · kitchen.ci, 30 Sept 2026
- 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. · kitchen.ci, 15 Oct 2026
- 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. · kitchen.ci, 30 Sept 2026
- Extensibility API
- The current driver contract documents the existing driver API behavior and implementation details for plugin authors. · kitchen.ci, 15 Oct 2026
- Installation
- Users can install the gem with gem install test-kitchen or install Cinc Workstation. · kitchen.ci, 15 Oct 2026
- License
- The project is released under the Apache License 2.0. · kitchen.ci, 15 Oct 2026
- Limit: abstraction overhead
- A G2 reviewer wanted the underlying Vagrant configuration exposed verbatim instead of abstracted behind Kitchen configuration. · g2.com, 15 Oct 2026
- Limitations
- The documentation says the kitchen-docker driver is currently without a maintainer and has known issues, and recommends kitchen-dokken instead. · kitchen.ci, 30 Sept 2026
- Limit: information discoverability
- A G2 reviewer said some recipe information was complicated to reach and look up. · g2.com, 15 Oct 2026
- Limit: learning curve
- A G2 reviewer said users need substantial DevOps knowledge and can spend hours resolving minor cookbook bugs. · g2.com, 15 Oct 2026
- 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. · kitchen.ci, 15 Oct 2026
- Limit: plugin availability
- Available drivers depend on which gems are installed in the particular Ruby, Cinc Workstation, or Chef Workstation environment. · kitchen.ci, 15 Oct 2026
- Limit: unmaintained Docker driver
- The driver documentation says kitchen-docker is currently without a maintainer and has known issues, recommending kitchen-dokken instead. · kitchen.ci, 15 Oct 2026
- Owner acquisition
- Progress Software completed its acquisition of Chef Software on October 5, 2020, for approximately $220 million in cash. · sec.gov, 15 Oct 2026
Where Test Kitchen stands on Freedom251
- Infrastructure Testing Tools#3 of 28