Test Kitchen vs wercker: What are the differences?
What is 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.
What is wercker? Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
Test Kitchen and wercker can be primarily classified as "Continuous Integration" tools.
"Automated testing" is the primary reason why developers consider Test Kitchen over the competitors, whereas "Automatic Deployments" was stated as the key factor in picking wercker.
Test Kitchen is an open source tool with 1.62K GitHub stars and 543 GitHub forks. Here's a link to Test Kitchen's open source repository on GitHub.