namemapping items recorded on windows 7 are not recognized on Windows XP x64

I have dot net application running on v4.0.

The same testcomplete project works fine on Windows 7 and above but has issues on Windows XP x64.

What kind of objects is it failing to recognize? Are they operating system driven, like file open, file save ...? If so, check out OpenFile and SaveFile  methods. Also conditional name mapping might help.



Good luck.



S

No, they are application specific like simple login screen controls username, password, ok button etc.

Even the main form which is the base form of all UI is not getting recognized.

Its working fine on Windows 7 but not on Windows XP.

Thanks in advance,
Shrirang

I am having a similar problem but in XP SP2 running on a VM. 



In my case the name mapping of our main screen changes as the test is executed.  This is new behavior discovered in TC9.20.  The main screen is a Windows Forms object.  Since almost all other mapping runs through this form, almost all other mapping becomes incorrect as well. 



There have been no changes to our application that might have caused this behavior. 



To troubleshoot I opened the tested application and reviewed the name mapping before running the application.  The mapping in the Object browser was correct before test execution.  As the test starts the mapping is correct and behavior is as expected.  Then our 'invoice process' is executed.  This takes about 5-7 minutes to complete.



During this time the mapping in Test Complete changes from the alias to nohing .

 

Prior to the invoice process, the 'enhanced .Net' object properties were displayed.  Somewhere in the middle  of the process, time test complete could not find the controls as the mapping had disappeared and the enhanced .Net properties were gone as well.  I had to stop Test Complete as it was in an loop waiting for an object that no longer was mapped to appear.



(.Net)

clrFullClassName: EnSite.Framework.FormHost

Before ****

(Standard) Name:WinFormsObject("FormHost")

WndClass: WindowsForms10.Window.8.app.0.3ce0bb8

MappedName: Aliases.Sys.Safari.FormHost



After ****

(Standard)

FullName: Sys.Process("SafariSuite").Window("WindowsForms10.Window.8.app.0.3ce0bb8", "EnSite Safari Suite®", 1)

Name: Window("WindowsForms10.Window.8.app.0.3ce0bb8", "EnSite Safari Suite®", 1)

MapppedName is blank



.Net Properties so ont appear.



Has anyone seen this type of behavior?



~Jon Conyers

Just FYI - When I had TC 8.7 installed on XP SP3, I could see the WinFormsObject items in the object browser. After installing TC 9.2, I now see Window objects in the browser instead. Changing the Method Invoke time out had no affect. Doing a Windows Update to get all the latest .Net updates did not help either. If I run the same program on Win7 (64bit) TC 9.2 object browser sees the WinFormsObject items OK.





I can just move my stuff to Win7 but if I needed to stay on XP, it seems I would be stuck at this point. I will be curious if anyone comes up with a solution.

Hi Tanya,



We are facing the same issue as well. We are currently using TC version 9.1.

On one of the machines (in a seaparate network) automation scripts work just fine.



On the other network, where we have around 5 VMs with test complete fails because the object appends WindowsForms10.Window.8.app. to the object name.



I have tested this on the sample application as well (orders.exe) - When used the object spy, on the form for the first time, the full name property value is set to "Sys["Process"]("Orders")["Window"]("WindowsForms10.Window.8.app.0.378734a", "Orders - Untitled", 1)" 



But when we spy it again and again (may be on the 2nd or 3rd time) it changes back to "Sys["Process"]("Orders")["WinFormsObject"]("MainForm")"





Can you please help us in resolving this issue.



Regards,

Chethan

Hi Tanya,



We have tried increasing the timeout to 120000 (120 secs).... this doesnt help.

Can you please us know a permanent fix for the same.



This has stalled all our test executions.



Regards,

Chethan