Sporadic problems with .NET WinForms object recognition in TC10.30
Hello,
We are experiencing a sporadic problem with .NET object recognition with a WinForms object. Most of the time, our .NET applications and child objects are being recognized correctly. But occasionally we get an unrecognized main form, which causes sets of tests to fail, and the errors flag our pipeline builds as bad. We’d like to eliminate the errors.
The form that is not being recognized successfully is a WindowsForms10 object (WinFormsObject when properly recognized). I have attached a screenshot showing the names of the first two levels of child objects of the Sys.Process(“<OurAppName>”) object when the form is not recognized.
Searching the forums, I’ve seen some older posts that seem to be related to this topic, and so I’ve collected the following information to help with figuring out what might be our problem.
Any assistance would be appreciated. Thanks.
We are experiencing a sporadic problem with .NET object recognition with a WinForms object. Most of the time, our .NET applications and child objects are being recognized correctly. But occasionally we get an unrecognized main form, which causes sets of tests to fail, and the errors flag our pipeline builds as bad. We’d like to eliminate the errors.
The form that is not being recognized successfully is a WindowsForms10 object (WinFormsObject when properly recognized). I have attached a screenshot showing the names of the first two levels of child objects of the Sys.Process(“<OurAppName>”) object when the form is not recognized.
Searching the forums, I’ve seen some older posts that seem to be related to this topic, and so I’ve collected the following information to help with figuring out what might be our problem.
.NET Open Application Support Plug-in – This plug-in is installed and enabled.
Method Invoke Timeout - From previous posts, we’ve seen that increasing the Method Invoke Timeout can help. We have increased this property to 30000 milliseconds. We have still experienced the recognition problem since making this change. (This change was made in the properties for the specific TestComplete project we are running, not in the Default project properties.)
Version - We are using TestExecute/TestComplete v10.30.1145.7
x86 vs. x64 - Our application is compiled as an x86 application.
Launch – The application is being launched via the TestApps collection. It is being launched in Simple Run Mode, and the application is being started after TestComplete/TestExecute has started processing the test. The application itself is started from a folder located off the Program Files (x86) folder. No specific custom Runtime Security policy settings are applied to where it is being run from.
Open Application Status – Most of the time, the application is detected as an open application and our tests run correctly. So the application is being treated as Open most of the time.
.NET versions – our application is targeting .NET v4.0. We’ve seen the issue on a couple of VM’s with different operating systems and installed .NET versions. One was a Windows 2008R2 system with .NET 4.5.1 installed, and another was Windows 2012R2 with .NET 4.5.2 installed. It should be noted that other runs on these same configurations worked fine, and this is a sporadic issue.
No Prior TC/TE Abnormal Terminations – as far as we can tell, TestExecute is starting and stopping normally during these automation runs.
Non-standard controls – The application is usually recognized as a WinForms application, and we are using DevExpress controls (XtraGrid, XtraVerticalGrid) in the application.
AppDomain objects in process – When the application form is not recognized as a WinFormsObject, there is an Sys.Process(“<process name>”).AppDomain(“<app name.exe>”) object present in the object tree. See attached screenshot for how it looks when we log it to the TestLog.
Any assistance would be appreciated. Thanks.
