Version: 7.10.0
Class: Chrome UI Functional Tests1.test/functional/apps/discover/_field_visualize路ts
Stack Trace:
Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="visualizeSaveButton"])
Wait timed out after 10014ms
at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/ossGrp1/TASK/saas_run_kibana_tests/node/linux-immutable/ci/cloud/common/build/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
at process._tickCallback (internal/process/next_tick.js:68:7)
at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)
Other test failures:
_Test Report: https://internal-ci.elastic.co/view/Stack%20Tests/job/elastic+estf-cloud-kibana-tests/845/testReport/_
Pinging @elastic/kibana-test-triage (failed-test)
Pinging @elastic/kibana-app (Team:KibanaApp)
Well, I caused these failures, I thought that cloud runs both OSS and Basic license so these tests are going to run only for an oss version.
Discover visualizes a field on the legacy visualizations for OSS and on Lens for Basic+. So these tests are testing the OSS navigation so they should be skipped on cloud as the Basic+ navigation is already tested on the x-pack functional tests cc @kertal
I think we are normally using isOss = await PageObjects.common.isOss(); for this - it's checking whether the non xpack tests are running in a xpack environment (like cloud)
Hmm, but I want to skip the whole test https://github.com/elastic/kibana/blob/master/test/functional/apps/discover/_field_visualize.ts#L36
not only some parts of the test.
Makes sense, in that case I think https://github.com/elastic/kibana/blob/851e7ff9b8ebc630fce766bab83c0f6d7ca7262c/test/functional/apps/visualize/_tile_map.js#L232 is better
Most helpful comment
Makes sense, in that case I think https://github.com/elastic/kibana/blob/851e7ff9b8ebc630fce766bab83c0f6d7ca7262c/test/functional/apps/visualize/_tile_map.js#L232 is better