Overhaul testing for kitchen-dokken #201
Closed
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
This is the smallest possible increment of initial testing, because I want to determine whether I understand what Travis is doing.
|
I'm going to close this down now. But I've made it slightly better using #263. We could really use a set of spec tests to know the default set of driver/provisioner options are actually useable with dokken. |
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.
Description
The existing tests are functional only in an unrealistic environment. It might be possible to make Travis successfully use docker-in-docker-in-docker, but that wouldn't necessarily say much about the software under test.
Issues Resolved
This will hopefully do something about #200