The solution to this problem is to declare the base Navigator to be dynamic which means that the list of the DOM elements underpinning that Navigator will be refreshed every time a method accessing the elements is called on it.ĭeclare version of SauceConnect to be used as part of the sauceConnect configuration. When the part of the DOM which contains elements of that Navigator is recreated, these references become stale causing any methods called on them to throw StaleElementReferenceException and their staleness cannot be rectified from within the code of the module method in question. This is because the reference to the base Navigator of a module is fixed at module creation time which in turn fixes the reference to the elements matching the selector used in the definition of that Navigator. Unfortunately this workaround is not available when an action performed as part of a method defined in a Geb module class causes the module base element to be re-rendered. Quite often the fact that DOM elements backing a Navigator have been removed from the DOM and redrawn can be worked around by creating a new instance of that Navigator by obtaining it from its content definition.
Unwrapping modules returned from the content DSL Accessing tag name, attributes, text and classes Creating directly from WebElement objects.
0 kommentar(er)
