Adding some very basic integration tests #112
Merged
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
hairyhenderson
force-pushed
the
add-integration-tests
branch
17 times, most recently
from
c888a4f to
efc63e1
Compare
Signed-off-by: Dave Henderson <[email protected]>
hairyhenderson
force-pushed
the
add-integration-tests
branch
from
6d0aeda to
f335708
Compare
hairyhenderson
changed the title
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.
It's high time some "integration" tests were part of the build. As in, actually running the
gomplatecommand in various scenarios that should work - especially ones that are hard to test during unit tests...First off, I want to be able to test the Vault integration with a real Vault server (in dev mode). So that's what most of these tests are.
This also moves the CI build to CircleCI 2.0.
Signed-off-by: Dave Henderson [email protected]