Convert acceptance tests to use test-kitchen #41
Merged
+66
−100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We're going to convert this over to use test-kitchen, so throw this on the ground.
Here we add a basic test-kitchen setup to add acceptance testing of an example site.pp in test/integration/default
Travis excludes development group; so doesn't have the kitchen tasks. Soft-require so that doesn't explode.
Drop all old puppets besides latest 3.x and 4.x. Add a cell to run the acceptance tests in docker.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test kitchen is far easier to wrangle and reason about than beaker or rspec-system, so convert over to using that.
In doing this I discovered a fair amount of rot in the travis matrix, so have replaced it with a far simpler matrix, testing just latest 3.x, 4.x, and acceptance testing in docker.
Closes #30