Implement End-To-End Integration Testing about kitchen-puppet HOT 5 CLOSED

How do you see the target?

• a dedicated repo or a subdir for end-to-end use cases?
• using the kitchen-docker driver as TravisCi now supports docker

from kitchen-puppet.

Tests should be part of the actual repo for sure, for CI solution i guess we need to look around, there is not only travis in the wild

from kitchen-puppet.

For the moment, I understand that "integration testing" would be "real kitchenci run with expectations about the results according to the provisionner flags". That means running kitchen-ci with a driver:

• I know for sure that TravisCI and CircleCI support docker (hence the kitchen-docker driver)
• we could also use other drivers like the digitalocean one but then these tests would not be "free" anymore
• I don't know if some CI in SaaS mode could support the vagrant driver

from kitchen-puppet.

@grubernaut , @looztra , @neillturner - please take a look at #96 .

There is simple working PoC of e2e test with Docker and Travis.

Please see relevant build in Travis https://travis-ci.org/neillturner/kitchen-puppet/builds/90233550

While it's really basic at the moment you can get the overall idea of how we can(easily) create e2e tests for kitchen-puppet.

Eager to hear you feedback!

from kitchen-puppet.

#96 will fix this issue when merged

from kitchen-puppet.