Hi bhakti,
It seems that you are using NameMapping do identify the components of the application. Am I right?
If so, you could one of the following:
1 - Make sure you get just one page(instance) of the application open. It's ALWAYS a good idea to have just 1 instance of the app open;
2 - I suggest you to record an action, a click(for example) on any component which are not being identified by TC and check the differences between the their Mapping;
Regards,
Leandro de Araújo Souza
2 - I suggest you to record an action, a click(for example) on any component which are not being identified by TC and check the differences between the their Mapping;
Regards,
Leandro de Araújo Souza
This is always the first thing we do. I'll often find a frame is somehow different and needs a wildcard to work. We are not testing two version of IE so I don't know if this applies. We are testing two applications which share the same NameMapping and found the wildcards very benificial. Hope this helps.
Could you send a screenshot of the error message, showing the element that was not identified and also a screenshot of the DOM of the element in the browser?
Regards,
Leandro de Araújo Sopuza
Sorry... I don't keep copies of the differences. I copy the before and after alias into Notepad++, compare, wildcard, and discard. For us, it's not always the object being identified but usually the frame which contains the object (which you'll see in the alias.
Here's the TC article (we've used wildcards in both the object and within the hierarchy to reach the object. http://support.smartbear.com/viewarticle/55789/
Hi william_roe,
It seems to me that you are an advanced TC user. But I have to ask: Have you rest assured this is not a problem of waiting for the "right time"? I mean waiting for the existence of the components. In order words, are you waiting/ checking for the existence of the componentes before using them?
I myself had lots of problems like these in the past. Hope this helps.
Regards,
Leandro de Araújo Souza
