-
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-8760] - Improve stability of Linode end-to-end tests #11350
test: [M3-8760] - Improve stability of Linode end-to-end tests #11350
Conversation
Coverage Report: ✅ |
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 pass
Do we need use the same timeout for rescue-linode.spec.ts
and update-linode-labels.spec.ts
?
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.
thank you!
We probably should! Not sure why I didn't tackle them to begin with, but just pushed that. Thanks @jaalah-akamai! |
Cloud Manager UI test results🎉 464 passing tests on test run #7 ↗︎
|
Cloud Manager E2E Run #6966
Run Properties:
|
Project |
Cloud Manager E2E
|
Branch Review |
develop
|
Run status |
Passed #6966
|
Run duration | 26m 43s |
Commit |
0fd6108529: test: [M3-8760] - Improve stability of Linode end-to-end tests (#11350)
|
Committer | jdamore-linode |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
2
|
Skipped |
0
|
Passing |
466
|
View all changes introduced in this branch ↗︎ |
Description 📝
Various improvements to our Linode end-to-end tests to reduce flakiness. Mostly revolves around increasing the Linode create timeout and ensuring the timeout is used in the tests.
Changes 🔄
Target release date 🗓️
N/A
How to test 🧪
(Pending)
Author Checklists
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 ✅