Need advice about which tool to choose?Ask the StackShare community!
Test Kitchen vs Vagrant: What are the differences?
Test Kitchen: Integration tool for developing and testing infrastructure code and software on isolated target platforms. Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire; Vagrant: A tool for building and distributing development environments. Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.
Test Kitchen and Vagrant are primarily classified as "Continuous Integration" and "Virtual Machine Management" tools respectively.
"Automated testing" is the primary reason why developers consider Test Kitchen over the competitors, whereas "Development environments" was stated as the key factor in picking Vagrant.
Test Kitchen and Vagrant are both open source tools. Vagrant with 18.6K GitHub stars and 3.74K forks on GitHub appears to be more popular than Test Kitchen with 1.62K GitHub stars and 543 GitHub forks.
Pros of Test Kitchen
- Automated testing6
- Detect bugs in cook books4
- Integrates well with vagrant2
- Can containerise tests in Docker2
- Integrates well with puppet1
Pros of Vagrant
- Development environments352
- Simple bootstraping290
- Free237
- Boxes139
- Provisioning130
- Portable84
- Synced folders81
- Reproducible69
- Ssh51
- Very flexible44
- Works well, can be replicated easily with other devs5
- Easy-to-share, easy-to-version dev configuration5
- Great3
- Just works3
- Quick way to get running2
- DRY - "Do Not Repeat Yourself"1
- Container Friendly1
- What is vagrant?1
- Good documentation1
Sign up to add or upvote prosMake informed product decisions
Cons of Test Kitchen
Cons of Vagrant
- Can become v complex w prod. provisioner (Salt, etc.)2
- Multiple VMs quickly eat up disk space2
- Development environment that kills your battery1
Sign up to add or upvote consMake informed product decisions
What is Test Kitchen?
What is Vagrant?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Test Kitchen?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Test Kitchen?
What tools integrate with Vagrant?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+33
+27
+39
+24
+35