Uploaded image for project: 'Magnolia Test Framework'
  1. Magnolia Test Framework
  2. MGNLTEST-204

VaadinWrapper::vaadinIsDone should "end gracefully"

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Duplicate
    • Critical
    • None
    • None
    • None

    Description

      We wrap most (all?) of the WebElement(s) with VaadinWrapper.
      When finding elements, we call #waitUntilVaadinIsDone.
      Since Vaadin is using async requests all the time, this seems to make sense in many cases -

      BUT we also have found cases, where Vaadin is never done - then endong up with a timeout-exceptions
      For instance this is the root-cause for the issue described in MGNLTEST-198.

      The JS-code of vaadinIsDone should stop at some point.
      Since we cannot really be sure whether Vaadin adds now async calls "constantly".
      Maybe we can restrict it to a max. number of "clients[client].isActive()" (see VaadinWebElementWrapper).
      When such max.number is reached - we should:

      • log that we stopped "earlier"
      • but return true in order to give selenium a chance to proceed

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cmeier Christoph Meier
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD