What is Test Kitchen?
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.
Test Kitchen is a tool in the Continuous Integration category of a tech stack.
Test Kitchen is an open source tool with 1.6K GitHub stars and 544 GitHub forks. Here’s a link to Test Kitchen's open source repository on GitHub
Who uses Test Kitchen?
8 companies reportedly use Test Kitchen in their tech stacks, including zombakka, 500px, and www.autotrader.co.uk.
17 developers on StackShare have stated that they use Test Kitchen.
Why developers like Test Kitchen?
Here’s a list of reasons why companies and developers use Test Kitchen
Test Kitchen Alternatives & Comparisons
What are some alternatives to Test Kitchen?
See all alternatives
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.