Andrei/opik 842/run tests against comet envs #1199
Open
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
AndreiCautisanu
force-pushed
the
andrei/OPIK-842/run-tests-against-comet-envs
branch
from
7e5768c to
493b4e2
Compare
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.
Details
First PR to add functionality for running integration e2e tests against Comet cloud environments (staging, dev, etc). The tests will be runnable once we create some tests accounts on our environments and store their credentials on Github Secrets. Currently only Staging environment has been configured in the setup fixtures, but that is easily expandable to the others once we decide how to do the test accounts.
Once all finished, tests should be able to run from the same GHA workflow, also added a README file to the tests_end_to_end directory on how to configure the environment and run the tests locally.