Jdmundrawala/test kitchen

@tyler-ball scared me today by pointing out that the windows_path change did not execute execute the fix immediately. This got me thing about how my testing could have missed such a thing, so I fired up test-kitchen and this all worked fairly painlessly for me, so I've decided to put it out there to get the conversation going. 

I was trying to run this locally to validate, but my Vagrant is failing to rename the host.  So!  I shall ask questions instead of running locally and observing.

Does the test automatically fail if the node does not converge using the supplied run_list?  If so, then you're right - the test currently validates that the node converges successfully.  But the test still _looks_ to me like it isn't validating anything.  If it automatically fails on node convergence failure, could you change the name or add a comment to that effect?

I think an even better test would be something like:

```ruby
describe "windws_path" do
  it "should update the path successfully" do
    # Node convergence occurs automatically
    expect(node.get_env).to match(/C:\\path_test_path/)
  end
end
```

I think this test does a better job of validating the `windows_path` code.  It checks to make sure the node converged successfully _and_ that windows_path performed its intended function.