Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(e2e): adjust the scripts to make it easier to run atlas cloud e2e tests locally #6425

Merged
merged 2 commits into from
Oct 30, 2024

Conversation

gribnoysup
Copy link
Collaborator

Small follow up to the new e2e capabilities to make it a bit easier to run these locally if needed. I adjusted the implies check in yargs parsing so that you can keep these env in your shell env config without triggering the implies check when not running the tests for cloud (you still need to explicitly provide the --test-atlas-cloud flag to trigger the test and it's still required to provide all the other options in that case, just not otherwise), also added some detailed instructions for what needs to be manually setup before running those, should be helpful also if we ever need to re-do the user creation

@gribnoysup gribnoysup added the no-title-validation Skips validation of PR titles (conventional commit adherence + JIRA ticket inclusion) label Oct 30, 2024
ATLAS_CLOUD_TEST_CLUSTER_CONNECTION_STRING_JSON="$(atlascli clusters connectionStrings describe $ATLAS_CLOUD_TEST_CLUSTER_NAME -o json)"
CONNECTION_STRINGS_JSON="$(atlascli clusters connectionStrings describe $ATLAS_CLUSTER_NAME -o json)"

export COMPASS_E2e_ATLAS_CLOUD_SANDBOX_CLOUD_CONFIG=$(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
export COMPASS_E2e_ATLAS_CLOUD_SANDBOX_CLOUD_CONFIG=$(
export COMPASS_E2E_ATLAS_CLOUD_SANDBOX_CLOUD_CONFIG=$(

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we are passing this to test-web-sandbox-atlas-cloud evergreen function (as qa), should we check if that's set?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or maybe remove it from there as we are now using MCLI_OPS_MANAGER_URL to determine this?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, can drop it from evergreen config, forgot about that, makes sense 👍

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in e284976 with the typo fix, thanks for spotting!

@gribnoysup gribnoysup merged commit ea204ef into main Oct 30, 2024
18 of 19 checks passed
@gribnoysup gribnoysup deleted the atlas-cloud-e2e-locally branch October 30, 2024 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-title-validation Skips validation of PR titles (conventional commit adherence + JIRA ticket inclusion)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants