The WebUI ftests are tested against a server with ES embedded which is usually faster (for a single concurrent user) than a production-like environment with a dedicated ES cluster. This causes random failures in some of the tests in certain environments Perhaps due to ES indexing/refreshing issues.
There are consistent test failures due to timeouts in the Collection.feature test, such as
Error: waitUntil condition timed out after 20000ms at Browser.waitUntil (/home/jenkins/workspace/integration-tests/nuxeo-server-web-ui/server-build-web-ui-build/nuxeo-web-ui-clone/node_modules/@wdio/utils/build/shim.js:276:24) at Browser.doesNotHaveCollection (/home/jenkins/workspace/integration-tests/nuxeo-server-web-ui/server-build-web-ui-build/nuxeo-web-ui-clone/packages/nuxeo-web-ui-ftest/pages/ui/browser.js:124:12) at World.<anonymous> (/home/jenkins/workspace/integration-tests/nuxeo-server-web-ui/server-build-web-ui-build/nuxeo-web-ui-clone/packages/nuxeo-web-ui-ftest/features/step_definitions/document.js:251:19)
The screenshots from these failures are attached.
- is required by
-
NXBT-3607 Add pipeline to validate the next Nuxeo version with the latest promoted Web UI version
-
- Resolved
-