-
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
[Discover] Unskip context navigation test #68490
[Discover] Unskip context navigation test #68490
Conversation
/** | ||
* the provides a quicker way to set the timepicker to the default range, saves a few seconds | ||
*/ | ||
async setDefaultAbsoluteRangeViaUiSettings() { |
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.
This should speed go the before
section of the test, since there is no interaction necessary to set the time range, however it seems it can't be measured in the jenkins stats of a single test run.
Pinging @elastic/kibana-app (Team:KibanaApp) |
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.
LGTM
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
# Conflicts: # test/functional/apps/context/_discover_navigation.js # test/functional/page_objects/time_picker.ts
Summary
Improved code testing the navigation between discover and discover context to be no longer flaky.
Here's a run just unskipping the test, 1 of 42 runs was a failure
https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/522/testReport/Chrome%20UI%20Functional%20Tests/
Here's the improved code version, 42 runs, no failure
https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/524/testReport/Chrome%20UI%20Functional%20Tests/
Fixes #53308
Checklist