When I obtain my process in a script (for instance, by using Sys.Process), the test execution is paused for too long. Why does this happen? Can I get rid off this?
A.: Most likely the application under test is an Open Application. When TestComplete retrieves a process object, it sends requests to all the processes running in the system to find Open Applications. TestComplete may freeze until it gets responses from these processes. So, if some of the processes are busy and cannot respond immediately, you may notice the delay. To avoid the problem, you may limit the number of applications to be requested: • Open your project in TestComplete. Switch to the Object Explorer panel. • Open the project editor and activate the Properties page. • Choose the Open Applications | Process filter settings group and specify the processes to be recognized as Open. • Save the changes. Now TestComplete will send requests only to those applications that you selected in the Process filter settings.
Related Questions
- When I obtain my process in a script (for instance, by using Sys.Process), the test execution is paused for too long. Why does this happen? Can I get rid off this?
- I am in the process of setting up a test, but I dont have a complete list of the requirements. What can I do to determine what to test and what to expect?
- What is the waiver process to obtain reimbursement for LOTE textbooks not on the SBOE approved list?
