Forum Discussion
11 years ago
Hi all,
Solution to this problem is very simple.
Just go to Testcomplete >> tools>> current project properties>> open aplication >> process filter and just select : use all processes,
Thats It, Now spy your objects and they will be recognized peoperly.
Problem was not with test complete version or method invoke timeout but it was lying beneath your process filter properties.
I hope you understood It Tanya, :)
Solution to this problem is very simple.
Just go to Testcomplete >> tools>> current project properties>> open aplication >> process filter and just select : use all processes,
Thats It, Now spy your objects and they will be recognized peoperly.
Problem was not with test complete version or method invoke timeout but it was lying beneath your process filter properties.
I hope you understood It Tanya, :)
- rfkbaboon7 years agoOccasional Contributor
Hi
I have a similar problem but solution that I should use all processes, doesn't help me.
I move my application and TestComplete from Windows 7 to Windows server 2016 and now TestComplete doesn't 'see' anything in application. When I try record script I've got an empty procedure.
for example one of the object in my application in object spy
before:
NameMapping.Sys.Process('NMultiLoader').WinFormsObject('MainForm').WinFormsObject('mainRibbon')
now:
Sys.Process('NMultiLoader').Window('WindowsForms10.Window.8.app.0.aec740_r9_ad1', 'ver. 2018.1 [LSI]', 1).Window('WindowsForms10.Window.8.app.0.aec740_r9_ad1', '', 2)