Selenium: User actions in the IE browser get triggered with a significant delay.

Problem:

User actions in the IE browser get triggered with a significant delay.

Solution:

The issue seems to be related to resource saturation of the test machine: it usually comes up when ~20 concurrent browsers are used on the same machine and is not so obvious with 10 concurrent browsers. The order in which IE is started does not seem to matter.
May be we need one node/server per IE?

Comments

Popular posts from this blog

Whitelist an Azure firewall IP using PowerShell

Excel: highlighting a row or a column based a value, the current date example.