Skip to main content

Performance Tips


Maximizing Test Execution In A Minimum Time Period#

Please note, if you are running your tests on a cloud based Selenium Grid then it may take a little longer time to complete an execution when compared with Local WebDriver execution. When running one to one sequential automation test threads, with LambdaTest cloud grid it may take around 1.3-1.5 times longer to complete the test depending upon the network latency.

To serve you better we are running multiple complementary services in our machines that perform various functions like take screenshots after every command given, capture complete test execution video logs, capture network logs, console logs etc. This takes a little bit processing power which when combined with network latency leads to higher overall test execution times.

You can certainly decrease this execution time by turning off the complimentary services though desired capabilities object. To decrease your test execution times you can set the below capabilities as "false" if these are set to "true":

  1. Visual: Enable step by step screenshot
  2. Network: Enable network logs
  3. Console: Capture console logs

Note: Console, network and visual capabilities are "false" by default.

Here's an example of such a capability object

DesiredCapabilities capabilities = new DesiredCapabilities();    capabilities.setCapability("build", "your build name");    capabilities.setCapability("name", "your test name");    capabilities.setCapability("platform", "Windows 10");    capabilities.setCapability("browserName", "Chrome");    capabilities.setCapability("version","79.0");    capabilities.setCapability("console",false);    capabilities.setCapability("network",false);    capabilities.setCapability("visual",false);

If you are facing any latency or slowness even after setting the above capabilities as "false", you can reach out to us on our in-app chat support or by emailing to [email protected] with a screenshot of trace-route command that would really help us checking the reason behind latency.

For Windows:

tracert hub.lambdatest.com

For Linux/Mac:

traceroute hub.lambdatest.com
Last updated on