Ryan_Moran
11 years agoValued Contributor
.net application plugin/support crashes during script playback
pseudo code:
Sys.Process("Infinity").WinFormsObject("frmCATFRAMS").someobject.click();
//after the control is clicked the application performs a CPU intensive task
Sys.Process("Infinity").WinFormsObject("frmCATFRAMS").someotherobject.click();
//this subsequent click now fails because the .Net support and extended object properties are failing
//the form name is now the generic: Sys.Process("Infinity").Window("WindowsForms10.Window.8.app.0.202c666", "INFINITY™ Version: 11.7.1.1", 1)
//restarting Test Complete or disabling all/then enabling all plugins will restore extended properties
Sys.Process("Infinity").WinFormsObject("frmCATFRAMS").someobject.click();
//after the control is clicked the application performs a CPU intensive task
Sys.Process("Infinity").WinFormsObject("frmCATFRAMS").someotherobject.click();
//this subsequent click now fails because the .Net support and extended object properties are failing
//the form name is now the generic: Sys.Process("Infinity").Window("WindowsForms10.Window.8.app.0.202c666", "INFINITY™ Version: 11.7.1.1", 1)
//restarting Test Complete or disabling all/then enabling all plugins will restore extended properties
- Tanya,
I was skeptical so I gave this a try.
Predictably this proposed solution had no impact on the issue I am experiencing.
If the .Find method times out during CPU intensive application processing extended properties are no longer available. I am still unable to work around this without setting the Auto-wait timeout to a value greater than the applications process time. From your code the "mainForm" in this scenario does exist, but is currently "Unresponsive" while processing....during that "Unresponsive" state I am performing a .Find on the form...
(mainForm.Find(prop,propVal,depth) )...the Find method appears to be waiting up until the auto-wait timeout and then causes the .Net plugin support to crash or become unavailable.