Forum Discussion
I guess the problem is related to automatic name mapping used while recording the script. While recording test complete will select a set of properties using which it guess it can identify the control uniquely during playback. But this will not be the case during playback. We can see the properties test completes selected to identify it from the name mapping file. Now we can run the application and right click over the control in name mapping tree and select Highlight on screen. The control will be highlighted over the UI if it can be identified uniquely. If we cannot identify the control, use the Object spy and drag over the control and identify the property that got a different value compared to name mapping file. Remove this property and try to identify a set of properties using which the control can be identified uniquely. Best practice might be to map the control manually to the namemapping file and then do a record if at all required