Integrating with LambdaTest

Automation now supports integration with LambdaTest. With this integration, Automation users can execute their tests on the LambdaTest cross-browser testing platform when using Automation.

LambdaTest is a cloud-based, quick, and reliable automation testing platform that expedites activities related to cross-browser testing for quicker and faster release cycles. LambdaTest lets you test against numerous browsers and operating systems. 

Automation’s integration with LambdaTest will make your cross-browser testing experience easier. You can choose from a wide range of Windows and Mac operating systems and all legacy and latest browsers. 

Configuring LambdaTest in Automation

To configure the LambdaTest app in Automation, you must have your LambdaTest credentials already set up.

Adding a Browser Provider

To begin configuring the LambdaTest App in Provar, add a new Browser Provider.

Navigate to Test Settings and click the Browser Providers tab. Click Add New (‘+’).

Above: View of Browser Providers tab.

The Add new Browser Provider screen is displayed. 

In Browser Provider section –

• In the Name field, enter the browser provider name. For example, LambdaTest. 
• In the Type field, select LambdaTest from the drop-down.

Above: Adding a new Browser Provider snapshot.

In the CrossBrowser Testing section –

• In the User Name field, enter your LambdaTest username to authenticate your test account. 
• In the Access Key field, enter your LambdaTest Access Token to authenticate your test account.

Note: For Access Key, you can copy the Access Token from LambdaTest. 

Above: Snapshot of Access Token in LambdaTest.

Click Test Connection to verify that your connection credentials are valid.

Adding Browsers

Next, add the browsers to be used.  In the Browsers section, click Add New (‘+’).

A new Add LambdaTest Browsers screen is displayed.

• The Browser Name field will be pre-populated based on the selections you make.
• In the Platform field, select the platform from the drop-down on which you want to test. 
• In the Web Browser field, select the web browser from the drop-down that you want to use for testing for the platform selected above.
• In the Browser Version field, select the browser version from the drop-down of the web browser that you selected in the above step. 

Note: You can also select Other from the drop-down instead of a specific version. For example, if you want to run your tests on the latest version of the selected browser and not from the one available in the drop-down. 

Select Other from the drop-down, and a text box Other is enabled. Enter a version supported by LambdaTest (other than the drop-down), and in the right format, then only your test case will run it will not. For example, if you want to run your test on the <latest> browser version supported by LambdaTest.

• In the Screen Resolution field, select the screen resolution that you want from the drop-down. 

Once you have entered the details, click OK. You can see the browser is added. The added browser provider is displayed in the Browser Providers tab.

Running Tests on LambdaTest

Once set up, tests can be executed in Run mode, Debug mode, or Run under ANT.

Run and Debug Mode Execution

To start executing test cases, select the new Web Browser you created above.

This can also be set for a particular test case by using the ‘Web Browser Override’ on the test’s Connection step.

Click Run or Debug to run the test. You can monitor the progress in the Test Runner.

On the LambdaTest Dashboard, you can monitor currently running and previously executed sessions.

Click on the session to see the details. You can see the project name and status of the running test case and information like browser, operating system, and resolution of the test cases.

Run under ANT execution

Provar also provides Run under ANT execution for LambdaTest for Desktop.

To select this, right-click on the test(s) or folder and select Run Under ANT.

In the ANT Dialog, select the new Web Browser you created above.

This will add the following parameters to the Build.xml file.

Running this file will initiate the session/run similarly to the above run and Debug mode sessions.

Proxy environments

When proxies are defined under Provar Network Settings, or are defined under the Desired Capability of the Browser Provider as a proxyURL; LambdaTest execution will work as expected.

Note: If proxy information is set up at both levels, Automation will prefer the proxy information in the Desired Capability setting in the Browser Provider.

To add a proxy at the Browser Provider level, open the Browser Provider in Edit and go to the Desired Capabilities section. Click Add New (‘+’).

On the Add new desired Capability screen, enter the name of proxyURL and the value. Click OK.

Once added, click Test Connection to ensure the connection works as expected.

Limitations

The following limitations currently exist in Automation’s implementation of LambdaTest.

Accessing Chrome profiles

Normally, when Automation’s test execution happens locally, Automation users can specify the Google Chrome profile that should be used in the execution. This is not supported when executing tests over Selenium Grid as the execution will happen at the remote node. Due to this limitation, you’ll need to re-provide a password and verification token when executing over Selenium Grid, or your IP will need to be whitelisted. Salesforce should know from where the request is coming so it can provide login access to execute the tests.

Accessing locally stored files

Generally, Automation allows you to download a file locally to perform actions such as assertions. This is not supported when executing tests on Selenium Grid because the remote node will not be able to access the locally downloaded file, so any tests that use locally downloaded files will not run successfully.

If you are affected by these limitations, please contact Provar support directly for advice.