All objects within NameMapping have been added automatically by the recording process. Until we started experiencing the random failures, I spent very little time reviewing/updating information in NameMapping.
I have a case already opened with SmartBear trying to figure out why NameMapping is creating all these different paths and how to correct. It's a mess for sure.
I'll review the information you provide and see if I can get things cleaned up. Thank you for responding.
While recording, anything you click on, it will automatically create a name mapping. Sometimes it will create duplicates, with different property values.
When you play this back, TC will get confused, as it doesn't know what actual object you are referring too!
I create name mappings based on the UI objects I will interact with, slowly building the tree structure. I use Object Spy and Object Browser to find my UI object, right click and select Map Object, followed by Choose a name and properties manually.
Object Name MappingIt is a slow process, but it works 100%
