KitchenCI (sometimes called Test Kitchen or simply Kitchen) is an open source software development tool for writing and testing infrastructure code and software on isolated target operating systems. It was originally developed to test Chef cookbooks (http://www.getchef.com/), but it is now being used across different configuration management systems (like Puppet, Ansible, and Salt).
Its target audiences are infrastructure developers, operations folks, and software developers that require their code to be executed in a production-like environment. It is a command line tool, the console is the user interface. Examples of console interaction are available in KitchenCI's Getting Started Guide, for example: http://kitchen.ci/docs/getting-star…g-converge.
As a tool that a developer or systems administrator would use, a simple workflow that stresses speed is a design goal. KitchenCI tries to reduce the complexity of setting up and running your code so that you can focus on code design and implementation. It has a very modular plugin architecture which gives the user freedom to run their code in whatever environment makes sense to them for their project. Similarly the user has freedom to choose their preferred testing language or framework (or none at all if they aren't ready to tackle testing yet).
In short, KitchenCI aims to give its users confidence in the code they write so that they can move faster, respond to change, and deliver more high quality products and services.