-
Notifications
You must be signed in to change notification settings - Fork 367
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
test: [M3-8979] - Fix lke-create test by using a different mock region #11411
Conversation
Coverage Report: ✅ |
Cloud Manager UI test results🎉 469 passing tests on test run #2 ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test looks good, thanks Azure! Were there more of these failures in other tests across CM as a result of using regions or other data unavailable in the staging environment? 😬
Reviewing this PR and running the tests locally made me realize an unrelated lke-create.spec.ts failure I need to fix - for anyone with the Kubernetes Enterprise
capability on their account, the final test in the spec is going to fail on local runs because we need to mock that the capability is not present, as the test expects. I'm going to include that in my changes for M3-8928.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests passing in staging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AzureLatte!
linode#11411) * Fix lke-create test by using a different mock region * Added changeset: Update mock region for LKE cluster creation test
Description 📝
The "can dynamically update prices when creating an LKE cluster based on region" test in lke-create.spec.ts fails when running against the staging API because only the Dallas region is available for LKE creation but the test assumes Newark is present. Fix the test by using a different mock region.
Changes 🔄
List any change(s) relevant to the reviewer.
How to test 🧪
To reproduce the issue locally you’ll want to set your REACT_APP_API_ROOT var in .env to the staging URL. You might also have to set REACT_APP_LOGIN_ROOT to the login staging URL, then run the following command
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅