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

Investigate random failures on 10.10 functional tests

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.10
    • Fix Version/s: 2.4.58
    • Component/s: Test Framework, UI

      Description

      A very common failure on the 10.10 functional tests is the test Create a new Search from another Saved Search, specifically the Create a new Search from another Saved Search69 I save my search as "PortugalFrance" (see here).

      It usually fails in the last step of the test feature. Error log bellow:

      [INFO]      [exec] 1) Create a new Search from another Saved Search69 I save my search as "PortugalFrance":
      [INFO]      [exec] element ("#actions paper-button") still not visible after 20000ms
      [INFO]      [exec] running chrome
      [INFO]      [exec] Error: element ("#actions paper-button") still not visible after 20000ms
      [INFO]      [exec]     at execute(<Function>, "#actions paper-button", true, , ) - wdio-shadow-plugin.js:174:10
      

      The goal is to investigate why this happens and check if we can solve or mitigate the problem to prevent random failures.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 1 hour
                  1d 1h

                    PagerDuty

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