Novari-QA
7 years agoFrequent Contributor
NameMapping inconsistant method of finding objects on screen
When name mapping my radio buttons I found out something very strange.
I would name map Radio Button #1 with no problem. The software states that I also have to map its parent panel. No problem. However, Radio Button #2 and #3 both require to name map the parent.parent.parent.parent.parent. etc etc etc etc.
Why is it that one object on the screen in the exact same location on the DOM tree requires less mapped objects while the other radio buttons require a ridiculously long list of parent objects? I dont care about 90% of the objects it is trying to map, how can I avoid this.