test-kitchen 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 77cb2e121e731f8ed40829e0761fc25e12f5fdc6
-  data.tar.gz: 511e9bfe61b61258cb2279daebf6e8c75b1c7334
+  metadata.gz: d22285218684802317ed183046f76c3cc2344292
+  data.tar.gz: ddebfec0f35d3e73146860e4f0c1965b5dcfa606
 SHA512:
-  metadata.gz: 7ad32bc4145eb26d101f62943edeb2bd8dd1279bf0c68f8db6184bd896be4728a3f812d09c83089608f0af900fa610355c8839927621c2bb58beeb2373dcd949
-  data.tar.gz: d86d1f63b5e655bce29e58cb2651aebe63edb4e519ba3a6514320f6c4c2f94b44d7e247c0a6f92395bef4494e6484251657b9d916f985bb00f8a1bac2ad5ad78
+  metadata.gz: dcc1ca63e1da958c70604f2df12fd141004f41339be28d815c593f5e1fa02b97005613dcd720dccc78fc2994ca82ce345b6a9e936efd50264e3883e4a36f87d5
+  data.tar.gz: 530e3634dc4113aa662f95aec7f8e5f49028fdaef173db54b172ff4253c9c8d79973b8b499823d6012d5c8f6307266eb7f7b5582e4180d5b79937fce1953d221

data/CHANGELOG.md

@@ -1,3 +1,14 @@
+## 1.1.0 / 2013-12-04
+
+### Default updates
+
+* Set `Busser[:sudo]` to `true` by default (formerly set to `false` by default). ([@fnichol][])
+
+### Improvements
+
+* Pull request [#272][]: Drive by typo fix. ([@kisoku][])
+
+
 ## 1.0.0 / 2013-12-01
 
 ### Bug fixes
@@ -371,6 +382,7 @@ The initial release.
 [#262]: https://github.com/opscode/test-kitchen/issues/262
 [#265]: https://github.com/opscode/test-kitchen/issues/265
 [#266]: https://github.com/opscode/test-kitchen/issues/266
+[#272]: https://github.com/opscode/test-kitchen/issues/272
 [@ChrisLundquist]: https://github.com/ChrisLundquist
 [@adamhjk]: https://github.com/adamhjk
 [@arangamani]: https://github.com/arangamani
@@ -390,6 +402,7 @@ The initial release.
 [@jrwesolo]: https://github.com/jrwesolo
 [@jtimberman]: https://github.com/jtimberman
 [@juliandunn]: https://github.com/juliandunn
+[@kisoku]: https://github.com/kisoku
 [@manul]: https://github.com/manul
 [@mattray]: https://github.com/mattray
 [@mconigliaro]: https://github.com/mconigliaro

data/README.md

@@ -1,135 +1,123 @@
 # Test Kitchen
 
+[![Gem Version](https://badge.fury.io/rb/test-kitchen.png)](http://badge.fury.io/rb/test-kitchen)
 [![Build Status](https://secure.travis-ci.org/test-kitchen/test-kitchen.png?branch=master)](https://travis-ci.org/test-kitchen/test-kitchen)
 [![Code Climate](https://codeclimate.com/github/test-kitchen/test-kitchen.png)](https://codeclimate.com/github/test-kitchen/test-kitchen)
+[![Dependency Status](https://gemnasium.com/test-kitchen/test-kitchen.png)](https://gemnasium.com/test-kitchen/test-kitchen)
 
-A convergence integration test harness for configuration management systems.
+|             |                                               |
+|-------------|-----------------------------------------------|
+| Website     | http://kitchen.ci                             |
+| Source Code | http://kitchen.ci/docs/getting-started/       |
+| IRC         | [#kitchenci][irc] channel on Freenode         |
+| Twitter     | [@kitchenci][twitter]                         |
 
-# Getting started
+> **Test Kitchen is an integration tool for developing and testing
+> infrastructure code and software on isolated target platforms.**
 
-Project Setup
--------------
+## Getting Started Guide
 
-Install the `test-kitchen` gem. `--pre` is necessary because Test Kitchen 1.0.0 has not been released yet.
+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:
 
-```text
-$ gem install test-kitchen --pre
 ```
+$ gem install test-kitchen
+```
+
+If you use Bundler, you can add `gem "test-kitchen"` to your Gemfile and make
+sure to run `bundle install`.
 
-This will expose the `test-kitchen` CLI. Run `kitchen init` to get started:
+Next add support to your library, Chef cookbook, or empty project with `kitchen
+init`:
 
-```text
+```
 $ kitchen init
-      create  .kitchen.yml
 ```
-In this guide, we
-will be using the [kitchen vagrant driver](https://github.com/test-kitchen/kitchen-vagrant),
-so install that:
 
-```text
-$ gem install kitchen-vagrant
-```
+A `.kitchen.yml` will be created in your project base directory. This file
+describes your testing confiuration; 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:
 
-Open up the `.kitchen.yml` file created in the root of your
-repository and modify it if you wish.
+```
+$ kitchen list
+```
 
-Now, it is time to get testing. Use the `--parallel` option to run
-your tests in parallel. Trust us, it's faster!
+Run Chef on an instance, in this case `default-ubuntu-1204`, with:
 
-    $ kitchen test
+```
+$ kitchen converge default-ubuntu-1204
+```
 
-### Helpful Switches
+Destroy all instances with:
 
- - `--destroy=always|passing|never`
-   - `passing` (default): destroy the machine after a successful test
-     run (which implies passing tests.)
-   - `never`: Never clean up builds, even if they pass or fail.
-   - `always`: Regardless of the success or failure of the build,
-     destroy the machine.
- - `--log-level=debug|info|warn|error|fatal` - Set the log-level of
-     the entire stack, including the chef-solo run.
+```
+$ kitchen destroy
+```
 
-You can also specify these switches in the `settings` has in your YAML:
+You can clone a Chef cookbook project that contains Test Kitchen support and
+run through all the instances in serial by running:
 
-```yaml
-settings:
-  parallel: true
-  destroy: never
+```
+$ kitchen test
 ```
 
-Options specified via the CLI still take precedence over options specified
-in the config.
-
-## The Kitchen YAML format
-
-Test-Kitchen reads its configuration from the .kitchen.yml
-configuration file at the root of your cookbook. It closely resembles
-the format of .travis.yml which is intentional.
-
-There are 4 stanzas in .kitchen.yml, driver_plugin, driver_config,
-platforms, and suites. driver_plugin, platforms, and suites are
-currently required. driver_config can optionally be used to set values
-for all platforms defined.
-
-The driver_plugin stanza is only one line long and defines which
-driver is used by test-kitchen.
-
-The platforms stanza defines individual virtual machines. Additional
-driver_config, node attributes, and run_list can be defined in this stanza
-
-The suites stanza defines sets of tests that you intend to be run on
-each platform. A run_list and node attributes can be defined for each
-suite. The run_list and node attributes will be merged with that of
-each platform. In case of the conflict, the attributes defined on the
-suite will triumph.
-
-```yaml
-
----
-driver_plugin: vagrant
-
-platforms:
-- name: ubuntu-12.04
-  driver_config:
-    box: opscode-ubuntu-12.04
-    box_url: https://opscode-vm.s3.amazonaws.com/vagrant/boxes/opscode-ubuntu-12.04.box
-
-- name: centos-6.3
-  driver_config:
-    box: opscode-centos-6.3
-    box_url: https://opscode-vm.s3.amazonaws.com/vagrant/boxes/opscode-centos-6.3.box
-  run_list:
-  - recipe[yum::epel]
-
-suites:
-- name: stock_system_and_user
-  run_list:
-  - recipe[user::data_bag]
-  - recipe[rvm::system]
-  - recipe[rvm::user]
-  attributes:
-    users:
-    - wigglebottom
-    rvm:
-      user_installs:
-      - user: wigglebottom
-        default_ruby: 1.8.7
+There is help included with the `kitchen help` subcommand which will list all
+subcommands and their usage:
+
+```
+$ kitchen help test
 ```
 
-## Overriding .kitchen.yaml with .kitchen.<driver>.local.yml
+## 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
 
-TODO
+## Authors
 
-## A Note
+Created and maintained by [Fletcher Nichol][fnichol] (<fnichol@nichol.ca>) and
+a growing community of [contributors][contributors].
 
-This project is currently in rapid development which means frequent releases,
-potential for massive refactorings (that could be API breaking), and minimal
-to no documentation. This will change as the project transitions to be used in
-production environments.
+## License
 
-Despite the warnings above, if you are still interested, please get in touch
-via freenode/IRC (#chef-hacking),
-Twitter ([@fnichol](https://twitter.com/fnichol)),
-or Email ([fnichol@nichol.ca](mailto:fnichol@nichol.ca)).
+Apache License, Version 2.0 (see [LICENSE][license])
 
-For everyone else, watch [this space](https://github.com/test-kitchen/test-kitchen).
+[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
+[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

data/lib/kitchen/busser.rb

@@ -37,7 +37,7 @@ module Kitchen
     # @option opts [String] :instance_ruby_bindir path to the directory
     #   containing the Ruby binary on the remote instance
     # @option opts [TrueClass, FalseClass] :sudo whether or not to invoke
-    #   sudo before commands requiring root access (default: `false`)
+    #   sudo before commands requiring root access (default: `true`)
     def initialize(suite_name, opts = {})
       validate_options(suite_name)
 
@@ -48,7 +48,7 @@ module Kitchen
       @config[:kitchen_root] = kitchen_root
       @config[:test_base_path] = File.expand_path(test_base_path, kitchen_root)
       @config[:suite_name] = suite_name
-      @config[:sudo] = opts.fetch(:sudo, false)
+      @config[:sudo] = opts.fetch(:sudo, true)
       @config[:ruby_bindir] = opts.fetch(:ruby_bindir, DEFAULT_RUBY_BINDIR)
       @config[:root_path] = opts.fetch(:root_path, DEFAULT_ROOT_PATH)
       @config[:version] = opts.fetch(:version, "busser")

data/lib/kitchen/cli.rb

@@ -68,7 +68,7 @@ module Kitchen
       end
     end
 
-    desc "diganose [(all|<REGEX>)]", "Show computed diagnostic configuration"
+    desc "diagnose [(all|<REGEX>)]", "Show computed diagnostic configuration"
     method_option :log_level, :aliases => "-l",
       :desc => "Set the log level (debug, info, warn, error, fatal)"
     method_option :loader, :type => :boolean,

data/lib/kitchen/version.rb

@@ -18,5 +18,5 @@
 
 module Kitchen
 
-  VERSION = "1.0.0"
+  VERSION = "1.1.0"
 end

data/test-kitchen.gemspec

@@ -9,9 +9,9 @@ Gem::Specification.new do |gem|
   gem.license       = 'Apache 2.0'
   gem.authors       = ['Fletcher Nichol']
   gem.email         = ['fnichol@nichol.ca']
-  gem.description   = %q{A convergence integration test harness for configuration management systems.}
+  gem.description   = %q{Test Kitchen is an integration tool for developing and testing infrastructure code and software on isolated target platforms.}
   gem.summary       = gem.description
-  gem.homepage      = 'https://github.com/test-kitchen/test-kitchen'
+  gem.homepage      = 'http://kitchen.ci'
 
   gem.files         = `git ls-files`.split($/)
   gem.executables   = %w(kitchen)

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: test-kitchen
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Fletcher Nichol
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-02 00:00:00.000000000 Z
+date: 2013-12-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: mixlib-shellout
@@ -248,7 +248,8 @@ dependencies:
     - - ~>
       - !ruby/object:Gem::Version
         version: '0.8'
-description: A convergence integration test harness for configuration management systems.
+description: Test Kitchen is an integration tool for developing and testing infrastructure
+  code and software on isolated target platforms.
 email:
 - fnichol@nichol.ca
 executables:
@@ -351,7 +352,7 @@ files:
 - templates/driver/version.rb.erb
 - templates/init/kitchen.yml.erb
 - test-kitchen.gemspec
-homepage: https://github.com/test-kitchen/test-kitchen
+homepage: http://kitchen.ci
 licenses:
 - Apache 2.0
 metadata: {}
@@ -371,10 +372,11 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.3
+rubygems_version: 2.0.14
 signing_key: 
 specification_version: 4
-summary: A convergence integration test harness for configuration management systems.
+summary: Test Kitchen is an integration tool for developing and testing infrastructure
+  code and software on isolated target platforms.
 test_files:
 - features/kitchen_command.feature
 - features/kitchen_driver_create_command.feature