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
In #221 , we added a feature to only derive, by default, the actions in the top-level widgets of the state. This default functionality allows TESTAR to derive only 1 set of actions per List dropdown. However, if we derive the actions in all the widgets of the state, TESTAR will derive a set of actions in each List dropdown, which is duplicated :/
The text was updated successfully, but these errors were encountered:
The UIA_ListControlTypeId element is created or detected twice by the UIAutomation API or the TESTAR UIA internals:
This provokes TESTAR to create duplicate widgets in the state of the applications, which subsequently provokes 2 other issues.
Potential issue hovering widgets in spy mode
In some Windows applications, this duplicated behavior may provoke users not to be able to hover over the desired widget that is on top of the state.
TESTAR_dev/windows/src/org/testar/monkey/alayer/windows/ElementMap.java
Lines 48 to 69 in ad9dc43
Duplicated actions
In #221 , we added a feature to only derive, by default, the actions in the top-level widgets of the state. This default functionality allows TESTAR to derive only 1 set of actions per List dropdown. However, if we derive the actions in all the widgets of the state, TESTAR will derive a set of actions in each List dropdown, which is duplicated :/
The text was updated successfully, but these errors were encountered: