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
Stabilize dashboard selenium tests #11004
Stabilize dashboard selenium tests #11004
Conversation
Passed once. Jenkins, test this. |
Passed twice Jenkins, test this. |
Third times not a charm. I'm wondering if this time another click failed because of the disappearing toast message. Will try more try wraps.
|
Iteration 2: passed once. Jenkins, test this |
Iteration 2: Passed twice Jenkins, test this |
Iteration 2: Third build was aborted. Jenkins, test this. |
Iteration 2: Passed three times. Jenkins, test this. |
* Convert default to named exports - errors * Make all error classes use class syntax and extends add tests * Extending Error apparently doesn't work * Merge PR #11004 to try to fix test failures
Iteration 2: Passed four times. |
Well, that's too bad. Still failing:
That message has been up for ~20 seconds so I think it might be unrelated to the errors. Looks like clicking the absolute link failed, but the |
Iteration 3: Passed Once |
Iteration 3: Passed Twice Jenkins, test this. |
* Convert default to named exports - errors * Make all error classes use class syntax and extends add tests * Extending Error apparently doesn't work * Merge PR elastic#11004 to try to fix test failures
Iteration 3: Passed Thrice. Jenkins, test this. |
Iteration 3: Fourth time aborted. Jenkins, test this. |
Iteration 3: Fourth time passing! I think this is ready to go. Rebasing to kick off another test. |
c11bf6c
to
fe4b4a4
Compare
build aborted. jenkins, test this |
fe4b4a4
to
be2f1b1
Compare
be2f1b1
to
e9cd1bd
Compare
* Convert default to named exports - errors * Make all error classes use class syntax and extends add tests * Extending Error apparently doesn't work * Merge PR elastic#11004 to try to fix test failures
@stacey-gammon Looks promising! Please don't merge this up yet. I think #10910 may supersede some of the these fixes. I'd also like to pull your fixes that my PR doesn't have. If this branch went into master, however, merging with mine will be nontrivial, so I'd like to avoid that if possible. |
@stacey-gammon Which flaky dashboard test(s) does this fix? I can keep an eye out for that as I run tests with these changes. |
np @archanid, sorry for the mix up, didn't realize you were actively working on this. One small additional change was fixing text Other than that it was mostly the toast notifications that were causing issues, so if your PR doesn't address that specifically, may want to close them purposefully. One of the most common failing tests was:
Thanks! |
// To avoid load errors in subsequent tests that refresh the index. | ||
bdd.it('Finish each test on the landing page', async () => { | ||
await PageObjects.dashboard.gotoDashboardLandingPage(); | ||
}); |
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.
Hmm.. Why make this an it
? There is no expect here. Shouldn't this just be an after
hook? Sounds like you want this to run at the end, so it would be an after all hook.
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.
Yup, that would make more sense. 👍 and be much more stable.
@stacey-gammon I've incorporated all of your changes into my PR. I haven't run it yet, will update when I do. |
Tests passing 🎉 🕺 🥇 |
Closing in favor of #10910 |
Attempt to fix #10980. Suspect a toast disappearing around the time
this gets clicked may be messing it up.