Error3 reports
Fix WebDriverError
in Kibana
✅ Solution
WebDriverError in Kibana functional tests often arises from timing issues or stale element references, especially with asynchronous UI updates. To resolve this, implement explicit waits using `browser.waitUntil` with a reasonable timeout before interacting with UI elements or asserting conditions. Also, refresh element references before use if changes to the DOM are expected.
Related Issues
Real GitHub issues where developers encountered this error:
Failing test: Chrome UI Functional Tests.src/platform/test/functional/apps/discover/tabs2/index·ts - discover/tabs "after all" hook: afterTestSuite.trigger in "discover/tabs"Jan 24, 2026
Failing test: Chrome UI Functional Tests.src/platform/test/functional/apps/discover/tabs2/_recently_closed_tabs·ts - discover/tabs recently closed tabs "after all" hook: afterTestSuite.trigger for "shJan 24, 2026
Failing test: Chrome UI Functional Tests.src/platform/test/functional/apps/discover/tabs2/_recently_closed_tabs·ts - discover/tabs recently closed tabs should push previous tabs to recently closed lisJan 24, 2026
Timeline
First reported:Jan 24, 2026
Last reported:Jan 24, 2026