Update Test Kitchen Setup for go-chef project

[mudash]

• Update Test Kitchen setup to make sure all existing test cases pass.
• Add test cases for newly added functionality for Policy File API calls.
• Implement /cookbook_artifacts end point for Policy file Cookbooks #19

Background: Test Kitchen cases was found when we refreshed go-chef from upstream. Need to make them work for us smoothly.

[MarkGibbons]

Upstream maintainer here. I had planned to eventually move the go code in the cmd directory, examples of using the go-chef api, to its own package. Since the code is all main functions at the moment it was going to take some refactoring. It looks like you want the code packaged this way:

go-chef/chef
        files *.go -> go modules in the go-chef/chef package
        test_chef_server - cookbook to spin up the server and run tests
              inspec tests
              test fixtures
              recipes to install the go code
        examples
            files *.go -> current cmd code turned into a separate package
            bin directory -> shell scripts to run the examples, called by the inspec tests

I do some weird things with the chefapi_test cookbook, mostly to be able to run the tests while developing and updating the api documentation.

Could I get some input on where you think the structure should go? I'd like to bring in your work, but the changes in structure make that difficult.

thanks,
Mark

[MarkGibbons]

I'm working on this refactoring in go-chef/chef.

[MarkGibbons]

I merged https://github.com/go-chef/chef/tree/test_refactor in the go-chef/chef repository. I think it does most of what you wanted out of a test kitchen refactor.