Add e2e tests #61
Open
Add e2e tests #61
Conversation
This file contains hidden or 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
…or to keep consustency
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.
This PR adds e2e tests for Injector.
test/e2eto follow the same pattern as in 1Password Operatortest/e2e/manifests- contains 2 deployments for the client app. Each uses either Connect or Service Account credentials to be able to test these 2 scenarious.test/e2e/client- contains simple client app in which secrets are injected.make test-e2ecommand which spins up kubernetes cluster and runs e2e tests against it.make build/secrets-injector- renamed todocker-buildto keep consystancy with 1Password Operator.github/workflows/test-e2e.ymlworkflow is added to run e2e tests.