-
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
FTR: Enable w3c for chromedriver #62542
FTR: Enable w3c for chromedriver #62542
Conversation
{ location: el, offset: { x: 200, y: 20 } }, | ||
{ location: el, offset: { x: 400, y: 30 } } | ||
{ location: el, offset: { x: -300, y: 20 } }, | ||
{ location: el, offset: { x: -100, y: 30 } } |
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 change tested on both chromedriver and msedgedriver
await browser.get(appUrl); | ||
// accept alert if it pops up | ||
const alert = await browser.getAlert(); | ||
await alert?.accept(); |
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.
According to W3C spec driver.get
call is not failing if alert pops up as before, but we need to accept it in order to proceed.
@elasticmachine merge upstream |
…/kibana into ftr/switch-chrome-to-w3c-mode
💛 Build succeeded, but was flaky
Test FailuresKibana Pipeline / kibana-oss-agent / Chrome UI Functional Tests.test/functional/apps/dashboard/dashboard_snapshots·js.dashboard app using current data dashboard snapshots compare area chart snapshotStandard Out
Stack Trace
History
To update your PR or re-run it, just comment with: |
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 - tested the discover tests with brushing the histogram on Chrome and Firefox on my local Windows.
* enable w3c for chrome * update maps tests * update maps tests * update common_page * Revert "update maps tests" This reverts commit 31f43fd. * revert changes to maps tests * undo after removal * update expect range to pass on Windows, unskip tests for Firefox * print out value for discover brushing test * log first timestamp Co-authored-by: Elastic Machine <[email protected]>
* enable w3c for chrome * update maps tests * update maps tests * update common_page * Revert "update maps tests" This reverts commit 31f43fd. * revert changes to maps tests * undo after removal * update expect range to pass on Windows, unskip tests for Firefox * print out value for discover brushing test * log first timestamp Co-authored-by: Elastic Machine <[email protected]>
* master: [APM] Change custom link from EuiListGroupItem to EuiLink (elastic#62742) [Remote Clusters] Update callout and move server_name field (elastic#62352) Removes Pitch Presentation Template from Canvas (elastic#62688) FTR: Enable w3c for chromedriver (elastic#62542) [ML] Disable functional tests [ILM] Skip failing API integration test (elastic#62779) [SIEM] Update beat doc (elastic#61902) [Search] Properly add slash preceding path in async search (elastic#62722) [APM] make sure environment query is correct for service maps… (elastic#62764) Add service map icon for rum-js agent type (elastic#62721) [APM] Service map - fixes irrelevant services on data refresh (elastic#62750) [APM] Service map - Fix taxi edge arrow orientation (elastic#62741) [APM] Prevent error rate alert trigger from rendering NaN (elastic#62754) [EPM] Store map visualizations from the package registry and use saved object ID (elastic#62059) [Alerting] for email action, set tls.rejectUnauthorized: false when secure: false (elastic#62380)
* enable w3c for chrome * update maps tests * update maps tests * update common_page * Revert "update maps tests" This reverts commit 31f43fd. * revert changes to maps tests * undo after removal * update expect range to pass on Windows, unskip tests for Firefox * print out value for discover brushing test * log first timestamp Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* enable w3c for chrome * update maps tests * update maps tests * update common_page * Revert "update maps tests" This reverts commit 31f43fd. * revert changes to maps tests * undo after removal * update expect range to pass on Windows, unskip tests for Firefox * print out value for discover brushing test * log first timestamp Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* enable w3c for chrome * update maps tests * update maps tests * update common_page * Revert "update maps tests" This reverts commit 31f43fd. * revert changes to maps tests * undo after removal * update expect range to pass on Windows, unskip tests for Firefox * print out value for discover brushing test * log first timestamp Co-authored-by: Elastic Machine <[email protected]>
* FTR: Enable w3c for chromedriver (#62542) * enable w3c for chrome * update maps tests * update maps tests * update common_page * Revert "update maps tests" This reverts commit 31f43fd. * revert changes to maps tests * undo after removal * update expect range to pass on Windows, unskip tests for Firefox * print out value for discover brushing test * log first timestamp Co-authored-by: Elastic Machine <[email protected]> * remove unused function * fix common page PO Co-authored-by: Elastic Machine <[email protected]>
Summary
Closes #34963 and unblock #61684
Webdriver became W3C standard, which means browser vendors implement drivers according the specification to have exact the same behaviour.
Recently we were running Chrome and IE drivers in non-W3C compliance mode (old way since Leadfoot times) and only Firefox in W3C mode. As the result, to make things work we had to split the driver logic like
Sometimes we had to split tests logic to support multiple drivers in different modes or even skip them (e.g.
skipFirefox
tag).The new chromium-based msedgedriver is fully W3C compatible and in w3c mode chromedriver works exactly the same way. It really makes sense to convert chromedriver run since we plan to drop IE 11 support and IEdriver from FTR, and we will be running all the drivers in W3C compliance mode.
Checklist
Delete any items that are not applicable to this PR.
For maintainers