[charts/argo-cd] Initial testing tests for validating Helm chart outputs # #183
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
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.
Investigation for #179
Checklist:
Chart.yamlfollowing Semantic Versioning.Changes are automatically published when merged to
master. They are not published on branches.This is a sample of the tests I've been writing as I work through the Argo Helm issues. I've found it particularly helpful for verifying initial issues and fixes and have added some comments around the validation I did for #171 and #181
It depends on an external project I've been working on in my spare time, which is a Terratest docker image with pre-populated golang tests. Source is here: https://github.com/seanson/terratest-helm-tester
I'm keen to get some feedback around how these tests work and if we think it is a workable flow in the future.