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 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.
https://github.com/TESTARtool/TESTAR_dev/blob/ad9dc431dde9cbdb2bb44588c6aece1a83d09744/windows/src/org/testar/monkey/alayer/windows/ElementMap.java#L48-L69
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 :/