You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When StaleElementReferenceException thrown framework should internally handle and should not break the execution if element present with new id or throw exception for element not present .
Actual behavior
if element exist in case of stale reference, it throws NullPointerException where command returns value for example getText
Works fine in case of commands that doesn't return value for example: Click, Clear, Sendkeys
Is the issue reproducible on runner?
Issue reproducible with code:
QAFExtendedWebElement ele = new QAFExtendedWebElement("locator");
ele.getText(); //should work
ele.setId("b421c72a-39b0-44d1-8d57-71b081e2eeee"); //mimic stale
ele.getText(); //java.lang.NullPointerException
The text was updated successfully, but these errors were encountered:
QAF Version:2.x
Expected behavior
When
StaleElementReferenceException
thrown framework should internally handle and should not break the execution if element present with new id or throw exception for element not present .Actual behavior
if element exist in case of stale reference, it throws
NullPointerException
where command returns value for examplegetText
Works fine in case of commands that doesn't return value for example:
Click
,Clear
,Sendkeys
Is the issue reproducible on runner?
Issue reproducible with code:
The text was updated successfully, but these errors were encountered: