medium10 pts · first answer countsui-automationseleniumpage-objects

The risk of @CacheLookup

In a Selenium PageFactory page object, adding @CacheLookup to a field made a test fail with StaleElementReferenceException after a list refreshed. Why?

A.The element was found once and reused, so the replaced DOM node went staleB.@CacheLookup makes Selenium look up the element on every single callC.@CacheLookup only works with XPath locators, not with CSS selectorsD.PageFactory fields cannot be used once the page has been reloaded

Discussion 0

Join free to post in the discussion.

The risk of @CacheLookup

Discussion 0

Related questions