My NameMapping changes with each run

Hi Kevin,

    

You can try using wild-card character asterisks (*) to get through this issue. To do this, open the NameMapping file, go to the object "Aliases.ceraexe0471.wndAfx.MDIClient.wndAfxFrameOrView8018", in the right pane the property value of object should display something like "wndAfxFrameOrView8018", edit this value and to remove the number and put an asterisks there. e.g. "wndAfxFrameOrView*". This should allow identification of object even though the number changes.



Regards,

Harshad Kashikar

Hi Harshad,



I was not able to rename wndAfxFrameOrView8018 in the Alias box, it gave me "is not a valid script identifier" error. I WAS able to successfully rename the WndClass to AfxFrameOrView*, but that didn't help. Any other suggestions?



Thanks,



Kevin Kleint

Hi Kevin,



From your code "Aliases.ceraexe0471.wndAfx.MDIClient.wndAfxFrameOrView8018.AfxWnd80.AfxWnd80", it seems that the parent object of  "AfxWnd80.AfxWnd80" also has some numbers postfixed which are also getting changed. Have you modified the properties of that object (wndAfxFrameOrView8018) as well in the NameMapping by putting anasterisks?



I would recommend you to check every parent object in the hierarchy, whether it is recognized by TestComplete or not. You can do that by doing right click on the object and selecting "Highlight on screen" option and see whether the object is actually getting highlighted or not. (Make sure that the object exists and is visible on screen before highlighting it).



If this also do not help,try using some other properties such as Name or any other property that can be used to recognized the object uniquely.



Regards,

Harshad Kashikar

Hi Kevin,





According to your screenshots, the value of the WndClass property can be variable too. Try using "Customer Service - John M. Doe*" or even "Customer Service*" as WndCaption value for identification.





BTW, I strongly recommend that you also remove all unnecessary objects like "AfxFrameOrView801", "AfxFrameOrView802", etc. from your Name Mapping scheme and leave only a single object - this will make your Name Mapping scheme easier to maintain.

Hi Allen,



Are you saying that I can bypass the "AfxFrameOrView80" value by mapping directly to the object? In my mind, if you map directly to the object, the mapped path must remain the same. Currently, the "AfxFrameOrView80" value changes each time a new test is run.



Thanks to everyone for their patience, I'm pretty new to this.



Kevin

Hi Kevin,

Are you saying that I can bypass the "AfxFrameOrView80" value by mapping directly to the object?

I'm not sure what you mean by "mapping directly to the object" here. However, here are the steps which should help:

1. Remove all "AfxFrameOrView80..." objects from your Name Mapping scheme (except for the original "AfxFrameOrView80" object).

2. Select the "AfxFrameOrView80" object in your Name Mapping scheme.

3. Specify the following recognition criteria:

WndClass = "AfxFrameOrView80*"

WndCaption = "Customer Service*"

4. Try playing back your test - it should work fine. If your recorded test uses the "AfxFrameOrView801", "AfxFrameOrView802", etc. objects, it would be better to re-record the problematic tests - if the Name Mapping scheme is correct, TestComplete will use the "AfxFrameOrView80" object this time and will not create new mappings for the object.

Hi, I know that the post is old, but I have a similar problem.



As you can see the screens below, every time I record a new test NameMapping "wndAfx" changes. This began to happen after that we started to build the application with Visual Studio 2010 (formerly VS 6). And if I run any tests, does not find "wndAfx" or "wndAfx1." Can anyone help me?



Thank you!

Hi Mateus,



You should either mask the variable part of the class with the '*' wildcard, as I suggested earlier, or, if multiple windows with similar classes will match this criteria, specify other, more reliable, recognition criteria for the window. For example, the value of the ControlID property should coincide with the numeric control identifier declared in your MFC application's sources (should be declared in resource.h, as far as I remember). Also, if you don't actually need to work with the problematic window, but need to access its child object(s), you can make TestComplete ignore the problematic object via the Extended Find feature (see the Using Extended Search Criteria for Mapped Object Identification help topic for more information).

Hi Allen,



Extended Find works fine. ty!

Hi Mateus,



Can you provide me some exact steps? I am also facing the same issue with wndafx. I folllowed some step from Allan slink but still it didnt worked for me. Thanks in advance.



Nikhil