Update .kitchen.yml to work against latest test-kitchen.

Author: Kartik Null Cating-Subramanian

.kitchen.yml

@@ -1,8 +1,6 @@
 ---
 driver:
-  forward_agent: yes
   name: vagrant
-  vm_hostname: false # do not bother trying to change the hostname (sometimes fails)
   customize:
     cpus: 2
     memory: 4096
@@ -14,20 +12,16 @@ provisioner:
   name: chef_zero
 
 platforms:
-  - name: windows_2012r2-chef11
+  - name: win2012-chef11
     driver_config:
-      box: win2k12r2
-      box_url: #insert your boxfile url here   
-      gui: true
+      box: windows-2012r2
     provisioner:
       require_chef_omnibus: 11.16.4
-  - name: windows_2012r2-chef12
+  - name: win2012-chef12
     driver_config:
-      box: win2k12r2
-      box_url: #insert your boxfile url here  
-      gui: true
+      box: windows-2012r2
     provisioner:
-      require_chef_omnibus: 12.3.0
+      require_chef_omnibus: latest
 
 suites:
   - name: default

CONTRIBUTING.md

@@ -36,9 +36,11 @@ a successful Chef run, but this is not absolutely required.
 ### Tests
 
 This cookbook is set up to run tests under [Test Kitchen](http://kitchen.ci/).
+You need to follow the latest instructions to have test-kitchen windows support
+configured on your machine.  For example, follow this
+[blog post](http://kitchen.ci/blog/test-kitchen-windows-test-flight-with-vagrant/)
 You should be able to run the ``bundle install`` and then ``bundle exec kitchen test``
-to run the integration tests. This will download an evaluation image of Windows and 
-run a couple of included recipes from the 'test' folder. You must have [VirtualBox](https://www.virtualbox.org/)
+to run the integration tests. You must have [VirtualBox](https://www.virtualbox.org/)
 and [Vagrant](https://www.vagrantup.com/) installed on your system. In the future we
 want to add [ServerSpec](http://serverspec.org/) tests as well.