Selenium geckodriver executes findElement 10 times slower than chromedriver (.Net)

Question

Sorry didn\'t find a similar question and maybe somebody can help.

Due to additional requirements we have to test our project not only with Chrome but with Firefox

Answer 1

Yep. You’re definitely hitting the performance issue that is part of .NET Core. It doesn’t happen on Chrome, IE, or Edge, because the driver executables for each of those browsers (unlike geckodriver) listen on both the IPv4 and IPv6 loopback addresses. If you were to specify “::1” as the host for geckodriver with .NET, the problem would disappear.

Refer to https://github.com/SeleniumHQ/selenium/issues/6597