test-kitchen 1.7.0 → 1.7.1.dev

data/CONTRIBUTING.md

@@ -1,14 +1,14 @@
-# Release Process
-
-This release process applies to all Test Kitchen projects, but each project may have additional requirements.
-
-1. Perform a Github diff between master and the last released version.  Determine whether included PRs justify a patch, minor or major version release.
-2. Check out the master branch of the project being prepared for release.
-3. Branch into a release-branch of the form `150_release_prep`.
-4. Modify the `version.rb` file to specify the version for releasing.
-5. Run `rake changelog` to regenerate the changelog.
-6. `git commit` the `version.rb` and `CHANGELOG.md` changes to the branch and setup a PR for them.  Allow the PR to run any automated tests and review the CHANGELOG for accuracy.
-7. Merge the PR to master after review.
-8. Switch your local copy to the master branch and `git pull` to pull in the release preparation changes.
-9. Run `rake release` on the master branch.
-10. Modify the `version.rb` file and bump the patch or minor version, and commit/push.
+# Release Process
+
+This release process applies to all Test Kitchen projects, but each project may have additional requirements.
+
+1. Perform a Github diff between master and the last released version.  Determine whether included PRs justify a patch, minor or major version release.
+2. Check out the master branch of the project being prepared for release.
+3. Branch into a release-branch of the form `150_release_prep`.
+4. Modify the `version.rb` file to specify the version for releasing.
+5. Run `rake changelog` to regenerate the changelog.
+6. `git commit` the `version.rb` and `CHANGELOG.md` changes to the branch and setup a PR for them.  Allow the PR to run any automated tests and review the CHANGELOG for accuracy.
+7. Merge the PR to master after review.
+8. Switch your local copy to the master branch and `git pull` to pull in the release preparation changes.
+9. Run `rake release` on the master branch.
+10. Modify the `version.rb` file and bump the patch or minor version, and commit/push.

data/Gemfile

@@ -1,19 +1,19 @@
-# -*- encoding: utf-8 -*-
-source "https://rubygems.org"
-gemspec
-
-group :guard do
-  gem "guard-minitest"
-  gem "guard-cucumber", "~> 1.4"
-  gem "guard-rubocop"
-  gem "guard-yard"
-end
-
-group :integration do
-  gem "berkshelf", "~> 4.3"
-  gem "kitchen-inspec", "~> 0.12.5"
-end
-
-group :test do
-  gem "codeclimate-test-reporter", :require => nil
-end
+# -*- encoding: utf-8 -*-
+source "https://rubygems.org"
+gemspec
+
+group :guard do
+  gem "guard-minitest"
+  gem "guard-cucumber", "~> 1.4"
+  gem "guard-rubocop"
+  gem "guard-yard"
+end
+
+group :integration do
+  gem "berkshelf", "~> 4.3"
+  gem "kitchen-inspec", "~> 0.12.5"
+end
+
+group :test do
+  gem "codeclimate-test-reporter", :require => nil
+end

data/Gemfile.proxy_tests

@@ -1,4 +1,4 @@
-# -*- encoding: utf-8 -*-
-eval_gemfile File.join(File.dirname(__FILE__), "Gemfile")
-
-gem "chef-config"
+# -*- encoding: utf-8 -*-
+eval_gemfile File.join(File.dirname(__FILE__), "Gemfile")
+
+gem "chef-config"

data/Guardfile

@@ -1,42 +1,42 @@
-# -*- encoding: utf-8 -*-
-ignore %r{^\.gem/}
-
-def rubocop_opts
-  { :all_on_start => false, :keep_failed => false, :cli => "-r finstyle" }
-end
-
-def cucumber_opts
-  cucumber_cli = "--no-profile --color --format progress --strict"
-  cucumber_cli += " --tags ~@spawn" if RUBY_PLATFORM =~ /mswin|mingw|windows/
-
-  { :all_on_start => false, :cli => cucumber_cli }
-end
-
-def yard_opts
-  { :port => "8808" }
-end
-
-group :red_green_refactor, :halt_on_fail => true do
-  guard :minitest do
-    watch(%r{^spec/(.*)_spec\.rb})
-    watch(%r{^lib/(.*)([^/]+)\.rb})     { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
-    watch(%r{^spec/spec_helper\.rb})    { "spec" }
-  end
-
-  guard :rubocop, rubocop_opts do
-    watch(%r{.+\.rb$})
-    watch(%r{(?:.+/)?\.rubocop\.yml$}) { |m| File.dirname(m[0]) }
-  end
-end
-
-guard :cucumber, cucumber_opts do
-  watch(%r{^features/.+\.feature$})
-  watch(%r{^features/support/.+$}) { "features" }
-  watch(%r{^features/step_definitions/(.+)_steps\.rb$}) do |m|
-    Dir[File.join("**/#{m[1]}.feature")][0] || "features"
-  end
-end
-
-guard :yard, yard_opts do
-  watch(%r{lib/.+\.rb})
-end
+# -*- encoding: utf-8 -*-
+ignore %r{^\.gem/}
+
+def rubocop_opts
+  { :all_on_start => false, :keep_failed => false, :cli => "-r finstyle" }
+end
+
+def cucumber_opts
+  cucumber_cli = "--no-profile --color --format progress --strict"
+  cucumber_cli += " --tags ~@spawn" if RUBY_PLATFORM =~ /mswin|mingw|windows/
+
+  { :all_on_start => false, :cli => cucumber_cli }
+end
+
+def yard_opts
+  { :port => "8808" }
+end
+
+group :red_green_refactor, :halt_on_fail => true do
+  guard :minitest do
+    watch(%r{^spec/(.*)_spec\.rb})
+    watch(%r{^lib/(.*)([^/]+)\.rb})     { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
+    watch(%r{^spec/spec_helper\.rb})    { "spec" }
+  end
+
+  guard :rubocop, rubocop_opts do
+    watch(%r{.+\.rb$})
+    watch(%r{(?:.+/)?\.rubocop\.yml$}) { |m| File.dirname(m[0]) }
+  end
+end
+
+guard :cucumber, cucumber_opts do
+  watch(%r{^features/.+\.feature$})
+  watch(%r{^features/support/.+$}) { "features" }
+  watch(%r{^features/step_definitions/(.+)_steps\.rb$}) do |m|
+    Dir[File.join("**/#{m[1]}.feature")][0] || "features"
+  end
+end
+
+guard :yard, yard_opts do
+  watch(%r{lib/.+\.rb})
+end

data/LICENSE

@@ -1,15 +1,15 @@
-Author:: Fletcher Nichol (<fnichol@nichol.ca>)
-
-Copyright 2012 Fletcher Nichol
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
+Author:: Fletcher Nichol (<fnichol@nichol.ca>)
+
+Copyright 2012 Fletcher Nichol
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/MAINTAINERS.md

@@ -1,23 +1,23 @@
-# Maintainers
-
-This file lists how the Test Kitchen project is maintained. When making changes
-to the system, this file tells you who needs to review your patch. You need a :+1: vote
-from at least 2 members of the project team listed below. Additionally, you need to not
-receive a veto from the Lieutenant or the Project Lead.
-
-## Project Lead
-
-* [Fletcher Nichol](https://github.com/fnichol)
-
-## Lieutenants
-* [Seth Thomas](https://github.com/cheeseplus)
-
-## Maintainers
-
-* [Adam Leff](https://github.com/adamleff)
-* [Jennifer Davis](https://github.com/iennae)
-* [Matt Wrock](https://github.com/mwrock)
-* [Steven Murawski](http://github.com/smurawski)
-* [Chris Hartmann](https://github.com/chris-rock)
-* [Sean Omeara](http://github.com/someara)
-* [Robb Kidd](https://github.com/robbkidd)
+# Maintainers
+
+This file lists how the Test Kitchen project is maintained. When making changes
+to the system, this file tells you who needs to review your patch. You need a :+1: vote
+from at least 2 members of the project team listed below. Additionally, you need to not
+receive a veto from the Lieutenant or the Project Lead.
+
+## Project Lead
+
+* [Fletcher Nichol](https://github.com/fnichol)
+
+## Lieutenants
+* [Seth Thomas](https://github.com/cheeseplus)
+
+## Maintainers
+
+* [Adam Leff](https://github.com/adamleff)
+* [Jennifer Davis](https://github.com/iennae)
+* [Matt Wrock](https://github.com/mwrock)
+* [Steven Murawski](http://github.com/smurawski)
+* [Chris Hartmann](https://github.com/chris-rock)
+* [Sean Omeara](http://github.com/someara)
+* [Robb Kidd](https://github.com/robbkidd)

data/README.md

@@ -1,135 +1,135 @@
-# Test Kitchen
-
-[![Gem Version](https://badge.fury.io/rb/test-kitchen.svg)](http://badge.fury.io/rb/test-kitchen)
-[![Build Status](https://secure.travis-ci.org/test-kitchen/test-kitchen.svg?branch=master)](https://travis-ci.org/test-kitchen/test-kitchen)
-[![Code Climate](https://codeclimate.com/github/test-kitchen/test-kitchen.svg)](https://codeclimate.com/github/test-kitchen/test-kitchen)
-[![Test Coverage](https://codeclimate.com/github/test-kitchen/test-kitchen/coverage.svg)](https://codeclimate.com/github/test-kitchen/test-kitchen)
-[![Dependency Status](https://gemnasium.com/test-kitchen/test-kitchen.svg)](https://gemnasium.com/test-kitchen/test-kitchen)
-[![Inline docs](http://inch-ci.org/github/test-kitchen/test-kitchen.svg?branch=master)](http://inch-ci.org/github/test-kitchen/test-kitchen)
-
-|             |                                               |
-|-------------|-----------------------------------------------|
-| Website     | http://kitchen.ci                             |
-| Source Code | http://kitchen.ci/docs/getting-started/       |
-| IRC         | [#kitchenci][irc] channel on Freenode, [transcript][irc_log] thanks to [BotBot.me][botbotme] |
-| Twitter     | [@kitchenci][twitter]                         |
-
-> **Test Kitchen is an integration tool for developing and testing
-> infrastructure code and software on isolated target platforms.**
-
-## Getting Started Guide
-
-To learn how to install and setup Test Kitchen for developing infrastructure
-code, check out the [Getting Started Guide][guide].
-
-If you want to get going super fast, then try the Quick Start next...
-
-## Quick Start
-
-Test Kitchen is a RubyGem and can be installed with:
-
-```
-$ gem install test-kitchen
-```
-
-If you use Bundler, you can add `gem "test-kitchen"` to your Gemfile and make
-sure to run `bundle install`.
-
-Next add support to your library, Chef cookbook, or empty project with `kitchen
-init`:
-
-```
-$ kitchen init
-```
-
-A `.kitchen.yml` will be created in your project base directory. This file
-describes your testing configuration; what you want to test and on which target
-platforms. Each of these suite and platform combinations are called instances.
-By default your instances will be converged with Chef Solo and run in Vagrant
-virtual machines.
-
-Get a listing of your instances with:
-
-```
-$ kitchen list
-```
-
-Run Chef on an instance, in this case `default-ubuntu-1204`, with:
-
-```
-$ kitchen converge default-ubuntu-1204
-```
-
-Destroy all instances with:
-
-```
-$ kitchen destroy
-```
-
-You can clone a Chef cookbook project that contains Test Kitchen support and
-run through all the instances in serial by running:
-
-```
-$ kitchen test
-```
-
-## Usage
-
-There is help included with the `kitchen help` subcommand which will list all
-subcommands and their usage:
-
-```
-$ kitchen help test
-```
-
-More verbose logging (for both test-kitchen and the chef-solo/chef-zero provisioners) can be specified when running test-kitchen form the command line using:
-
-```
-$ kitchen test -l debug
-```
-
-## Documentation
-
-Documentation is being added on the Test Kitchen [website][website]. Please
-read and contribute to improve them!
-
-## Versioning
-
-Test Kitchen aims to adhere to [Semantic Versioning 2.0.0][semver].
-
-## Development
-
-* Source hosted at [GitHub][repo]
-* Report issues/questions/feature requests on [GitHub Issues][issues]
-
-Pull requests are very welcome! Make sure your patches are well tested.
-Ideally create a topic branch for every separate change you make. For
-example:
-
-1. Fork the repo
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
-
-## Authors
-
-Created and maintained by [Fletcher Nichol][fnichol] (<fnichol@nichol.ca>) and
-a growing community of [contributors][contributors].
-
-## License
-
-Apache License, Version 2.0 (see [LICENSE][license])
-
-[botbotme]: https://botbot.me/
-[contributors]: https://github.com/test-kitchen/test-kitchen/graphs/contributors
-[fnichol]: https://github.com/fnichol
-[guide]: http://kitchen.ci/docs/getting-started/
-[irc]: http://webchat.freenode.net/?channels=kitchenci
-[irc_log]: https://botbot.me/freenode/kitchenci/
-[issues]: https://github.com/test-kitchen/test-kitchen/issues
-[license]: https://github.com/test-kitchen/test-kitchen/blob/master/LICENSE
-[repo]: https://github.com/test-kitchen/test-kitchen
-[semver]: http://semver.org/
-[twitter]: https://twitter.com/kitchenci
-[website]: http://kitchen.ci
+# Test Kitchen
+
+[![Gem Version](https://badge.fury.io/rb/test-kitchen.svg)](http://badge.fury.io/rb/test-kitchen)
+[![Build Status](https://secure.travis-ci.org/test-kitchen/test-kitchen.svg?branch=master)](https://travis-ci.org/test-kitchen/test-kitchen)
+[![Code Climate](https://codeclimate.com/github/test-kitchen/test-kitchen.svg)](https://codeclimate.com/github/test-kitchen/test-kitchen)
+[![Test Coverage](https://codeclimate.com/github/test-kitchen/test-kitchen/coverage.svg)](https://codeclimate.com/github/test-kitchen/test-kitchen)
+[![Dependency Status](https://gemnasium.com/test-kitchen/test-kitchen.svg)](https://gemnasium.com/test-kitchen/test-kitchen)
+[![Inline docs](http://inch-ci.org/github/test-kitchen/test-kitchen.svg?branch=master)](http://inch-ci.org/github/test-kitchen/test-kitchen)
+
+|             |                                               |
+|-------------|-----------------------------------------------|
+| Website     | http://kitchen.ci                             |
+| Source Code | http://kitchen.ci/docs/getting-started/       |
+| IRC         | [#kitchenci][irc] channel on Freenode, [transcript][irc_log] thanks to [BotBot.me][botbotme] |
+| Twitter     | [@kitchenci][twitter]                         |
+
+> **Test Kitchen is an integration tool for developing and testing
+> infrastructure code and software on isolated target platforms.**
+
+## Getting Started Guide
+
+To learn how to install and setup Test Kitchen for developing infrastructure
+code, check out the [Getting Started Guide][guide].
+
+If you want to get going super fast, then try the Quick Start next...
+
+## Quick Start
+
+Test Kitchen is a RubyGem and can be installed with:
+
+```
+$ gem install test-kitchen
+```
+
+If you use Bundler, you can add `gem "test-kitchen"` to your Gemfile and make
+sure to run `bundle install`.
+
+Next add support to your library, Chef cookbook, or empty project with `kitchen
+init`:
+
+```
+$ kitchen init
+```
+
+A `.kitchen.yml` will be created in your project base directory. This file
+describes your testing configuration; what you want to test and on which target
+platforms. Each of these suite and platform combinations are called instances.
+By default your instances will be converged with Chef Solo and run in Vagrant
+virtual machines.
+
+Get a listing of your instances with:
+
+```
+$ kitchen list
+```
+
+Run Chef on an instance, in this case `default-ubuntu-1204`, with:
+
+```
+$ kitchen converge default-ubuntu-1204
+```
+
+Destroy all instances with:
+
+```
+$ kitchen destroy
+```
+
+You can clone a Chef cookbook project that contains Test Kitchen support and
+run through all the instances in serial by running:
+
+```
+$ kitchen test
+```
+
+## Usage
+
+There is help included with the `kitchen help` subcommand which will list all
+subcommands and their usage:
+
+```
+$ kitchen help test
+```
+
+More verbose logging (for both test-kitchen and the chef-solo/chef-zero provisioners) can be specified when running test-kitchen form the command line using:
+
+```
+$ kitchen test -l debug
+```
+
+## Documentation
+
+Documentation is being added on the Test Kitchen [website][website]. Please
+read and contribute to improve them!
+
+## Versioning
+
+Test Kitchen aims to adhere to [Semantic Versioning 2.0.0][semver].
+
+## Development
+
+* Source hosted at [GitHub][repo]
+* Report issues/questions/feature requests on [GitHub Issues][issues]
+
+Pull requests are very welcome! Make sure your patches are well tested.
+Ideally create a topic branch for every separate change you make. For
+example:
+
+1. Fork the repo
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request
+
+## Authors
+
+Created and maintained by [Fletcher Nichol][fnichol] (<fnichol@nichol.ca>) and
+a growing community of [contributors][contributors].
+
+## License
+
+Apache License, Version 2.0 (see [LICENSE][license])
+
+[botbotme]: https://botbot.me/
+[contributors]: https://github.com/test-kitchen/test-kitchen/graphs/contributors
+[fnichol]: https://github.com/fnichol
+[guide]: http://kitchen.ci/docs/getting-started/
+[irc]: http://webchat.freenode.net/?channels=kitchenci
+[irc_log]: https://botbot.me/freenode/kitchenci/
+[issues]: https://github.com/test-kitchen/test-kitchen/issues
+[license]: https://github.com/test-kitchen/test-kitchen/blob/master/LICENSE
+[repo]: https://github.com/test-kitchen/test-kitchen
+[semver]: http://semver.org/
+[twitter]: https://twitter.com/kitchenci
+[website]: http://kitchen.ci