Forum Discussion
jenli
15 years agoContributor
Hi Allen,
See my answers to your questions:
1. A possible cause of the problem is that some complex actions which take long to be completed are performed in the application's GUI threads when the application is started (the application's main window may become blank or unresponsive in such cases). If so, try increasing the "Method invoke timeout" option described in the "Project Properties - General Open Applications Options" help topic, check whether the problem persists and let us know your results.
Sure, our WPF application is very complex. When this occured, the application's main window does not become blank and is responsive to my manual GUI actions but my testscript can no longer find the top WPF window. After I increased the "Method invoke timeout" to 30000. The frequency of this probelm has been reduced.
When this problem occured, I wnet to Object Broswer and saw my WFP application is still recognized as Open application but as Open Window application not Open WPF application.
2. What version of TestComplete are you using (Help | About...)? If it is earlier than TestComplete 7.52 (the latest version of TestComplete 7), please update the tool and check whether the problem persists in this version.
We are using Testcomplete 7.52.
3. Is your tested application compiled for an x86 platform or for an x64 platform?
Our tested application is compiled for an x86 platform.
4. Exactly how is the application launched? Is it launched as an item of the Tested Applications collection? Is it launched under another account (in the RunAs mode)? Is it launched before or after TestComplete is launched? Please send us a detailed description of the steps you follow to launch the application.
I have tried the different approaches to launch the my WPF application. Normally, it is launched as an item of the Tested Applications.collection as:
TestedApps.myWPFApplicationName.Run(1, true);
I also tried to lauch the application before and after TestComplete is launched. This still occurs. To resolve this, I tried to launch the application several times or just reboot my testing computers.
5. Is the application launched from a network folder or from a folder having specific Runtime Security Policy settings? If it is, please make sure that the Runtime Security Policy settings for the folder from which the application is started are set as it is described in the "Working With Network and No-Touch-.NET-Deployment Applications" help topic.
The application is launched from my local disk folder.
6. Is the application treated as Open according to the Process Filter options? Please see the "Project Properties - Process Filter Options" help topic for details.
Yes.
7. The problem can be caused by the fact that TestComplete is terminated incorrectly and the tested application is not restarted after that. Is this your case?
No.
8. Does your application's process have child objects named "AppDomain(...)" when the application is not recognized as Open?
My WPF application is always recognized as Open but not as WPF application but as Window application or occasionally under the process, it was recognized UIAObject.
See my answers to your questions:
1. A possible cause of the problem is that some complex actions which take long to be completed are performed in the application's GUI threads when the application is started (the application's main window may become blank or unresponsive in such cases). If so, try increasing the "Method invoke timeout" option described in the "Project Properties - General Open Applications Options" help topic, check whether the problem persists and let us know your results.
Sure, our WPF application is very complex. When this occured, the application's main window does not become blank and is responsive to my manual GUI actions but my testscript can no longer find the top WPF window. After I increased the "Method invoke timeout" to 30000. The frequency of this probelm has been reduced.
When this problem occured, I wnet to Object Broswer and saw my WFP application is still recognized as Open application but as Open Window application not Open WPF application.
2. What version of TestComplete are you using (Help | About...)? If it is earlier than TestComplete 7.52 (the latest version of TestComplete 7), please update the tool and check whether the problem persists in this version.
We are using Testcomplete 7.52.
3. Is your tested application compiled for an x86 platform or for an x64 platform?
Our tested application is compiled for an x86 platform.
4. Exactly how is the application launched? Is it launched as an item of the Tested Applications collection? Is it launched under another account (in the RunAs mode)? Is it launched before or after TestComplete is launched? Please send us a detailed description of the steps you follow to launch the application.
I have tried the different approaches to launch the my WPF application. Normally, it is launched as an item of the Tested Applications.collection as:
TestedApps.myWPFApplicationName.Run(1, true);
I also tried to lauch the application before and after TestComplete is launched. This still occurs. To resolve this, I tried to launch the application several times or just reboot my testing computers.
5. Is the application launched from a network folder or from a folder having specific Runtime Security Policy settings? If it is, please make sure that the Runtime Security Policy settings for the folder from which the application is started are set as it is described in the "Working With Network and No-Touch-.NET-Deployment Applications" help topic.
The application is launched from my local disk folder.
6. Is the application treated as Open according to the Process Filter options? Please see the "Project Properties - Process Filter Options" help topic for details.
Yes.
7. The problem can be caused by the fact that TestComplete is terminated incorrectly and the tested application is not restarted after that. Is this your case?
No.
8. Does your application's process have child objects named "AppDomain(...)" when the application is not recognized as Open?
My WPF application is always recognized as Open but not as WPF application but as Window application or occasionally under the process, it was recognized UIAObject.
Related Content
- 12 months agosanket2799
- 3 years agoMichal_Ignaczak
- 12 months agolalit_singh