-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Testing: Skip flaky e2e tests #30344
Conversation
@@ -23,7 +23,7 @@ class CustomEnvironment extends JSDOMEnvironment { | |||
} | |||
|
|||
async teardown() { | |||
await this.global.editorPage.stopDriver(); | |||
await this.global.editorPage?.stopDriver(); |
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.
I'm not sure this is a good fix, mainly a hunch to see if it fixes the instability.
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.
stopDriver
being undefined is usually the result of a failure with something else. But I understand that it causes confusion to see this error. I think it should be fine to have this change.
Size Change: 0 B Total Size: 1.42 MB ℹ️ View Unchanged
|
The first iOS one seems to be related to GitHub servers returning a 500 error during an artifact upload. We did a few fixes (1, 2, 3) recently with iOS tests and they should be quite stable. The second Android one is indeed flakiness, but We're currently working on adding a different kind of e2e test for mobile here, some changes we introduce there should get rid of this Android flakiness. And this time we're making sure it's very robust before merging it by running them consecutively multiple times. |
Thanks for looking at this. Flaky tests lead to apathy in regarding failures. It's better to quarantine tests that have hiccups and revisit them |
To have more confidence in our test suite, we need to maintain a stable suite and avoid flaky tests as much as we can. So we should fix them ideally or skip them until they're made stable.
This PR takes a look at the latest commits in master and skips the tests that are flaky.