Create tests for different configurations of Vagrantfile/manifests

[jtreminio]

Need to more completely cover the end result. Not the vagrant-puppet-lamp code, but what is generated by puphpet directly.

Will need refactor Puphpet\Controller\Front::createAction() and separate out the twig stuff from the file generation stuff from the download file stuff.

Will need to more strictly define what values are valid for each input field from website, and create random data from valid values.

Then we can run multiple tests through puppet-lint to see if our stuff builds.

[staabm]

Maybe this is helpfull https://puppetlabs.com/blog/release-management-blog/video-continuous-integration-for-your-puppet-code/

[frastel]

I currently think about compiling the complete manifest from fragments. This could be done like the file configurator mechanism I added in the master recently (or even better event based). Means some configurator can register on manifest manipulation (webserver configurator, database configurator, php configurator etc.). When the configuration matches for the configurator it will execute otherwise it will idle (nginx configurator adds only something to the manifest when webserver == 'nginx').
In this way we could create really simple tests for each partial + configurator and drop the complex and huge manifest test.