Specs for my Vagrant / Chef Solo based workflow.
It is intended for testing whether the environment in which it is used has all the prerequisites installed and that the common scenarios can be excercised. It also serves as the acceptance tests for Bill's Kitchen (a Chef/Vagrant development environment for Windows) and my Linus' Kitchen (a Chef/Vagrant development environment inside an Ubuntu VM).
The common scenarios are centered around:
- A sample-toplevel-cookbook with all kinds cookbook tests: syntax check, style checks, linting, unit and integration tests
- A sample-infrastructure-repo which defines a sample server infrastructure with environments and databages via Vagrant / Chef Solo
You are in a development environment with Git, Vagrant (>= 1.6), and the following Vagrant plugins installed:
- vagrant-omnibus - installs omnibus chef in a vagrant VM
- vagrant-berkshelf - berkshelf integration for vagrant
- vagrant-toplevel-cookbooks - support for one top-level cookbook per vagrant VM
Whenever you think you are in a sane environment, you can excercise the workflow specs like so:
git clone https://github.com/tknerr/vagrant-workflow-tests
cd vagrant-workflow-tests
rspec
You should see an output like this and all tests should pass: