-
Notifications
You must be signed in to change notification settings - Fork 8.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
Flaky test code - dashboard add panel and accident clicks on add new visualization
#20819
Comments
I'm seeing similar occasional failures running tests locally from master. My thought is that when the test clicks the Add menu item and that panel flys out, there's a query to Elasticsearch for the list of visualizations and the savedObjectFinderSearchInput isn't editable until that query returns.
I'm trying a try loop in services dashboard add_panel filterEmbeddableNames(name) |
Discovered that there is a loading indicator on the table. While it's loading it has these classes; So we should add code to wait for that loading indicator to go away before trying to setValue on the filter. I'll work on a PR for it. |
@LeeDr Mind if I re-open this? I suspect that PR, while helpful, did not fix the issue with flyouts. |
@stacey-gammon did you actually figure out how this could happen? |
nope, just a suspicion. I'm attempting to isolate some of these dashboard tests to see if the failure still exists after your changes to verify, but being pulled into test reviews, so haven't had time yet. I have this PR which passed the last run: #21225 But perhaps I should try running one that was being hit more often, or the |
Removing the version labels: we should not be assigning version until the PR is merged. |
Pretty sure this has been fixed when animations was disabled |
@bmcconaghy ran into a flaky test locally and we figured out that what was happening (or at least strongly suspect) is that the flyout transitioning from left to right and simulatenously having selenium attempt to type in a visualization to search for was causing accidental navigation to the add visualization page.
The screenshot is one of the visualization page, hence it can't find the search input box anymore. We should modify the tests so that when we open or close a flyout we wait for the transition to be complete before continuing on with any other test code.
Doesn't seem to be causing failures on master (yet), but I wouldn't be surprised if it starts at some point.
cc @liza-mae (since you've been working on a lot of flaky test stuff, thought you might want to be aware of this one).
Output:
The text was updated successfully, but these errors were encountered: