CAPABILITY GENERATOR

LambdaTest DocumentationAutomation Testing ● JavaScript With Selenium – Running JavaScript Automation Scripts On LambdaTest Selenium Grid

JavaScript With Selenium – Running JavaScript Automation Scripts On LambdaTest Selenium Grid


LambdaTest Selenium Automation Grid is a cloud based scalable Selenium testing platform which enables you to run your automation scripts on 2000+ different browsers and operating systems. You can now run your JavaScript Selenium automated test cases on a scalable Selenium infrastructure that is running real browsers and real operating systems.

This post will help you in getting started with configuring and running your JavaScript based automation test scripts on LambdaTest Selenium cloud platform. This topic will help you:

  • Run a sample Selenium Webdriver test using JavaScript on LambdaTest Automation.
  • To comprehend and configure Selenium test suite with respect to your capabilities.
  • Selecting the specific browsers to run your test on.
  • Dig deeper in the advanced features of LambdaTest.
  • To run your test cases in parallel to reduce build times.
  • To test your locally hosted pages.

Prerequisites For Running JavaScript With Selenium


Before getting started with Automated Scripts on LambdaTest Automation with JavaScript, you need to:

  • Make sure to use the latest version of JavaScript.
  • Download Selenium JavaScript bindings from the official website. Latest versions of Selenium Client and WebDriver are ideal for running your automation script on LambdaTest Selenium cloud grid.
  • Install npm from the official website by clicking here.
  • Download Lambda Tunnel binary file if you wish to test your locally hosted or privately hosted projects.
  • Although, it isn’t necessary, but it is always recommended to use a test automation framework. You can use Protractor for JavaScript.

Getting Started With JavaScript and Selenium


The first step in using LambdaTest platform is to understand LambdaTest’s Selenium Grid capabilities. Our Selenium Grid uses remote webdriver instead of normal Selenium client browser drivers so if you are migrating from locally run Selenium, you would have to invoke LambdaTest Selenium remote webdriver. Next you need to specify in your code, which browser, browser versions, operating systems, and resolution you wish to run your test on, along with defining LambdaTest specific capabilities. You can checkout LambdaTest Capabilities Generator tool to understand more about how you can define running browser environments and leverage advanced LambdaTest capabilities.

Let us begin with a simple Selenium Remote Webdriver test first. The JavaScript below tests a simple to-do application with basic functionalities like mark items as done, add items in a list, calculate total pending items etc. You can also find this at our JavaScript GitHub repository.

Below is the config.js file where we will be declaring the desired capabilities.

The Selenium Webdriver test would open a URL, mark the first two items in the list as done, add an item in the list, and return the total number of pending item. Your results would be displayed on the test console (or command-line interface if you are using terminal/cmd) and on LambdaTest dashboard. LambdaTest Dashboard will help you view all your text logs, screenshots and video recording for your entire Selenium tests.

Execute The Test

You would need to execute the below command in your terminal/cmd.

Running First Test

Understanding & Configuring JavaScript Desired Capabilities


As we said earlier the first step is to configure your test scripts to connect with LambdaTest Selenium automation gird. In the above mentioned JavaScript code, the first thing you would notice is the invoking of remote webdriver instead of the native browser webdrivers. So for example if you are planning to run on Firefox browser in your local machine, you would be using Firefox browser driver like this:

Local Browser Code

Since now you are performing the tests on LambdaTest’s Firefox browser, the code has to be modified a bit. To run the code on Firefox browser hosted by LambdaTest, you’d need to add the following command to your existing JavaScript code:

Remote Web Driver

In the JavaScript code, we are passing browser, browser version, and operating system information, along with LambdaTest Selenium grid capabilities via capabilities object.

Our Capabilities Generator will automatically generate the program, based on your provided input. For Instance, if you select the below configurations:

Fields
Selected Values
Operating System
Windows 8.1
Browser
Mozilla Firefox
Browser Version
62.0
Resolution
1280×1024
Selenium Version
3.11.0

Then Capabilities Generator at LambdaTest will provide you with the below program:


The most important capabilities to understand here are ‘browserName’, ‘versions’, and ‘platform’. They define which browser environment you wish to run the test on. Rest of the capabilities are important in test management and debugging. We have a inbuilt capabilities generator tool as well that you use to generate capabilities code for your test suite.

Advanced LambdaTest Capabilities


In addition to default Selenium Grid capabilities, LambdaTest also has platform specific capabilities like video recording of test runs, console logs of each test run, network logs of each test run, custom profiles for specific browsers, etc. Do checkout our documentations on LambdaTest Advanced capabilities as well.

Testing Locally Hosted or Privately Hosted Projects


LambdaTest allows you to test your locally hosted or privately hosted websites or web applications with the help of Secure Shell (SSH) Tunnel connection. Lambda Tunnel allows you to test your website or web-pages for cross browser compatibility even before they go live. You can connect your local server with LambdaTest’s Secure Cloud server using SSH tunnel and can perform cross browser testing on LambdaTest’s Selenium browser grid. You can also perform testing from different geo locations having different IP addresses and also test the applications secured with your organization’s firewall. To learn more about LambdaTest Secure Shell Tunnel refer to our complete documentation on Lambda Tunnel.

To get started with Lambda Tunnel, you can download our binary tunnel fine (.zip) and then extract it

Once you extract the file, you need to enter the following command in your command terminal. Make sure that you redirect the pointer to the same folder in which you’ve extracted the tunnel file.

So, let’s assume if your email ID is myemailid@gmail.com and your user access key is 123asd321 then you’ll need to run the following command in command terminal.

Once you get a message that your ‘Secure connection established, you may start your tests now’ , you need to enter the following code in your JavaScript code block:

You can also add the capability using LambdaTest Capabilities Generator.

Tunnel Reference: For a full reference of all tunnel features we support, visit our tunnel page.

Mark Test As Pass Or Fail


While performing automation testing using Selenium with JavaScript on LambdaTest Selenium grid, it is imperative to flag an automation test as either pass or fails. This is completely dependent on your testing requirement with respect to the validation of expected behaviour. You can mark whether an automation test passed or failed by adding the below code fragment in your automation script:

Parallel Testing


Parallel Testing is one of the most demanding features of LambdaTest Selenium Grid. By parallel testing, you can run more than one test case, simultaneously. This means that Parallel testing would allow you to execute numerous automation test cases altogether. So you execute a single test scenario across different browsers or could run different test scenarios across the same browser but with different browser versions. Wondering how many parallel test cases can you run? That depends entirely on the number of concurrent session under your opted plan.

For instance, if you have a bucket of 100 automated test cases, and the average time for execution of a single test is around 6 minutes. The time taken normally to completely execute all your test cases sequentially would be 600 minutes i.e. 10 hours. However, if you are opting for a plan which offers 2 concurrent sessions then you can perform 2 parallel test cases. This would divide your time in half as the total time taken through parallel testing with 2 concurrent sessions for the above scenario would be 300 minutes i.e. 5 hours. Similarly, if you have got 4 concurrent sessions with you then the time taken would be quarter with respect to sequential testing. This way you could fasten your release cycles as much as you want.

Test automation frameworks like Protractor are really useful in running parallel tests. For instance, in our above example, you may notice that we are running our test in a single environment. If you want to cover multiple environments you would have to change the hard code every time. Or you would have to use arrays, or multi-threading or something similar.

With LambdaTest, you can pace up your test build activities by performing parallel automation testing using Selenium with JavaScript and Protractor. Boost quality assurance of your product by performing extensive and fast-paced automated cross browser testing process with LambdaTest parallel testing.

Checkout the same code below to understand it better. You can also find it at our github page here.

To perform parallel automated testing using LambdaTest Automation in JavaScript with Selenium.

Parallel Testing Example

Here is parallel conf which executes the same tests in parallel.

If you notice, with simple annotations and parameters, you can now run your test suite on multiple browsers every time, without changing the browsers parameters in code files every time.

Queuing


To prevent over-exploitation of the platform we have added a capacity constraint on the number of tests that can be queued at our platform. Your maximum queue capacity will be dependent upon the number of concurrent sessions your LambdaTest account is eligible for. Below formula will help you calculate the maximum capacity for your queue.

Maximum Queuing Capacity

Maximum number of parallel tests that can be queued = n + 150

Here, n = number of concurrent sessions.

For instance, if you are opting for a pricing where you can avail up to 10 concurrent sessions. Then the maximum number of test cases that can be queued will be equal to 10 + 150 i.e. 160 queued test cases. LambdaTest would automatically schedule and execute test cases for you.

LambdaTest Queuing Policy

Here you can get more information about LambdaTest Queuing Policy.

Queuing Timeout

There is also a limit on how long a test case can stay in the queue. If your test case stays in the queue for more than 15 minutes, the test case would be timed out and would not be executed.

Related Articles