IE under Windows 10 too slow
Hi, recently my computer was upgraded to Windows 10. For the last year I've successfully run many keyword tests with plenty of clickItem operations on combo box items. Now under Windows 10 these...
Forum Discussion
There is an option under Tools -> Options -> Engines -> General for "Enable support for testing Windows store applications". By default, that is turned on. Try disabling that option, restarting TestComplete, and see if you get a performance increase.
You can also try this:
Preparing Internet Explorer for Web Testing
Disable Multiple Processes of Internet Explorer
Internet Explorer 9 and later spawn multiple iexplore.exe processes. This feature is called Loosely-Coupled Internet Explorer (LCIE) and is designed to improve the browser’s reliability and session isolation.
You must disable LCIE for Internet Explorer 11 on Windows 10. For other Internet Explorer versions, disabling LCIE is optional but can improve test performance.
To disable LCIE:
-
Click Start and select Run. In the Run dialog box, type regedit and press Enter. This will open the Registry Editor.
-
Find the following key:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main
-
In this key, find the TabProcGrowth value.
If this value does not exist, create a new DWORD (32-bit) Value and name it TabProcGrowth.
-
Set the TabProcGrowth value to 0.
-
Close the Registry Editor.
This will instruct Internet Explorer to run the frame window and all of the tabs within the same iexplore.exe process rather than multiple processes.
Thank you for your reply.
I added TabProcGrowth with a value of 0 to the registry and unchecked "Enable support for testing Windows store applications".
I also followed all other steps of "Preparing Internet Explorer for Web Testing".
Unfortunatly the problem stays the same.
I know you don't want to go through and edit all your clickitem instances... but something to try at least as a POC, right before one of your "clickitem" calls, also make a call for the same object to execute the method/action "scrollIntoView" with a parameter set to "true". It's possible that the upgrade to Windows 10, with your application (especially if the component is inside a frame inside the page), that TestComplete's "auto scroll" capability may be hampered. I've seen this happen in our own systems. Explicitly calling "scrollIntoView" as I mentioned will alleviate that problem.
At least give it a try in one instance to see if it resolves the problem.
Thank you.
I will definitely give it a try. Maybe this will take some time, because the error does not always occur at the same clickItem operation, but after I have a result I will post a response here again.
