Uploaded image for project: 'Nuxeo Web UI'
  1. Nuxeo Web UI
  2. WEBUI-778

Make functional tests consistent in production-like environments

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.x
    • Component/s: CI/CD

      Description

      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.  

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tfowley Thomas Fowley
                Reporter:
                tfowley Thomas Fowley
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.