We have released version 0.6.0 of Test Kitchen. Thanks to Eric Wolfe, this release decouples RVM, so runtimes must be specified explicitly to run integration tests. We felt that this would be the least surprising thing for the most common current use of test kitchen: testing cookbooks.
You can also use your data bags via Vagrant’s built in data bag path feature if they’re present. This should help lots of cookbooks that use data bag items in a local chef-repository. Thanks Brendan Hay, for implementing this!
Project’s configurations can now inherit the runtimes from the parent project, so it doesn’t need to be specified on a per-configuration basis. Thank you Chris Roberts.
--platform command line option for
kitchen test will now work, and requires specifying the full platform and version. For example:
kitchen test --platform ubuntu-12.04
Test Kitchen is released as a RubyGem. You can install it with
gem install. If you pinned the version in a Gemfile for your project, you’ll need to update that. Bundler will use the new version automatically if you install with
- [KITCHEN-29] – –platform flag doesn’t work for test command.
- [KITCHEN-37] – Let projects inherit runtimes from parents
- [KITCHEN-22] – Include Databags in Vagrant Configuration if present
- [KITCHEN-35] – use the minitest-handler in community.opscode.com rather than andew crump’s fork
- [KITCHEN-4] – decouple rvm use for running integration/unit tests