The .travis.yml file could only work if you have a github url. Just adding the .travis.yml file with a <fill in github repo here> seems like a good starting point.

As far as testing of a config, you assume the kitchenplan script works, but you want to make sure that everything compiles and installs that is in the config files. The best solution would be that you could run `provision` with a --test option that merges all config files into one big one. The only problem is if you have conflicting recipes somewhere, but normally this won't be an issue. 

I suggest we move the testing to another issue and finish up this pull request since this will make it better, and we can see when there is time to focus on more testability.