Articles in this section

See more

Configuring a Remote Agent, Browser Stack, Sauce Labs, Selenium Grid and other Environment in LEAPWORK

Avatar
Rishi Gaurav
  • Updated
Follow

Agent Configuration

LEAPWORK supports the execution of automation flows on remote machines. This allows flows to run uninterrupted and gives the opportunity to run the same flow in different configurations.
In LEAPWORK, environments define the available machines/devices where the automation flows can be executed. The chosen agents can be used when defining schedules or when running automation flows in preview mode. 

LEAPWORK ships with 6 types of Environment, each offering different capabilities:

The following describes how to create a new agents and walks you through the different environment types in detail:
 
Creating an Agent
To configure a LEAPWORK Environment, launch the LEAPWORK studio and follow the below steps:
Step 1: In LEAPWORK Studio, Navigate to the “Environment” section.

mceclip1.png

Step 2: Click on “New” button from the Agent menu.

A Pop-up window “Create New Environment” will appear as below:

Environment Types

Remote (Agent)

The Remote Agent is the LEAPWORK proprietary run-time agent used for distributed test execution. This type of environment can be used for Web, Desktop UI, and Virtual Desktop testing. To set up an environment as a Remote (Agent), first select the Environment type* as Remote (Agent) from the drop-down and then provide the value for below fields:

mceclip0.png

  1. Specify a unique title for the environment, e.g. “Local Agent”, “Remote Agent” or simply “Agent” etc.
  2. If the Agent is installed on the same machine as the LEAPWORK Studio, the hostname can be specified as “localhost”. In other cases specify the IP address, machine name, or DNS name for the remote machine.
  3. The port should match the port specified as part of the LEAPWORK Agent installation on the remote machine. The default port is 6777 but can be changed if needed.
  4. If a password was specified as part of the agent installation, enter this password. Otherwise, leave it blank.
  5. Choose the wanted screen resolution used when executing automation flows on the remote machine. The list contains the available resolutions on the remote machine.
  6. The primary display (denoted as Display 1) is the default display; however, in the case of multiple displays, a particular display for test execution should be selected.

      7. The description is an optional field which can be used to keep some notes/descriptions about                the environment.

      8. Lock the session after disconnecting from agent

      9. Authentication. There are three types of authentication:-

  • Windows Login:- This is used to authenticate connections to the agent with a Windows username and password.
  • Windows login-auto:- This is used to automatically login to the agent with a predefined Windows username and password on each connection.
  • Password:-It is used to login to Windows using a simple password.     

After specifying all values, test the environment by clicking ‘Test connection’. If the environment is set up correctly, LEAPWORK will open a terminal window and show the desktop of the host computer. At this point, you can choose to login with the Windows account that you want the agent to run with. This login will remain until the agent machine is restarted.

Save the configuration and this is ready to be used. See more information about this environment type here.

 

Web Only – Selenium Grid

A Selenium Grid is basically a Selenium proxy with several Aelenium agent machines. When the automation flow runs in the LEAPWORK controller, it will send the instructions to the Selenium Grid instead of to a LEAPWORK agent.

Watch our Setting up a Selenium Grid video to get more information about the Selenium Grid and how to use it with LEAPWORK.

To set up with Selenium Grid, first select the Environment type* as Web Only – Selenium Grid from the drop-down and then provide the value for the below fields:

mceclip1.png

  1. Specify a unique title for the environment,e.g. “Selenium Grid”.
  2. Specify the IP address, machine name or DNS name for the Hub of Selenium Grid.
  3. The port should match the port specified as part of the Selenium Grid configuration. The default port is 4444 but can be changed.
  4. “Platform name” is an optional field and should only be specified if the testing is required to be done on a specific platform available on Selenium Grid, otherwise it can be left blank.
  5. Choose the browser from the available drop-down list on which testing is required as a part of this environment configuration.
  6. The browser version can be specified if a test has to be executed on a specific browser version. However, to test a specific version, the version should be available on Selenium Grid. Otherwise, just leave the field blank to run tests on any available version of the specified browser.
  7. Choose the wanted browser resolution to use when executing automation flows.
  8. The description is an optional field which can be used for keeping some notes/description about the environment.
  9. The user profile is used if certain plug-ins, extensions, bookmarks, etc. are required while initializing test cases. Users can create custom profiles on Chrome and Firefox browsers which are saved on the local path of a machine.

  10. With the Chrome browser users can automate web applications on Desktop, Phone, Tablet, and Laptop. Below are the options available under the 'Device type' section

    • ‘Desktop’: Use this option to automate web applications on desktop machines
    • ‘Phone, Tablet and Laptop’: Choose any desired option from the drop-down
    • ‘Custom’: Users can define custom devices by specifying width, height, pixel rate, and user-agent. Landscape/Portrait mode settings can be achieved by specifying width and height as per the device.

    Please note that the device type section will be available only when ‘Browser to start’ is set to ‘Chrome’.

After specifying all values, test the connection by clicking ‘Test connection’. If the environment is set up correctly LEAPWORK will show a ‘Successfully connected’ message.

The Selenium Grid with specified a platform and browser is ready to be used. 

You can find more information about setting up a Selenium Grid in this tutorial. You can find more information about Selenium Grid in general [here]

Web Only – Sauce Labs

Sauce Labs is a cloud-based platform for automated testing of web and mobile applications.

Watch this video to learn more about how to set up an environment for Sauce Labs.

In order to create an environment pointing to a Sauce Labs device, you need to create an account with Sauce Labs.

Select the ‘Environment type*’ as Web Only – Sauce Labs from the drop-down and then provide the value for below fields:

mceclip2.png

  1. Specify a unique title for the environment, e.g. “Saucelab_WIN_FF”.
  2. Saucelabs account Username must be provided.
  3. Saucelabs account Access Key must be specified.
  4. Choose the desired “Platform & OS” from the available list of the drop-down.
  5. For the specified platform, choose the platform version from the available drop-down list on which testing is required as a part of this environment configuration.
  6. Choose the browser from the available drop-down list on which testing is required as a part of this environment configuration.
  7. The browser version can be specified in case a test has to be executed on a specific browser version. However, if the version information is not available, “latest” should be chosen as the option.
  8. Choose the wanted screen resolution used when executing automation flows on the SauceLabs machine.
  9. The description is an optional field which can be used for keeping some notes/description about the environment.

After specifying all values, test the connection by clicking ‘Test connection’. If the environment is set up correctly, LEAPWORK will show a ‘Successfully connected’ message.

Web Only – Browser Stack

Browser Stack is a cloud-based cross-browser testing tool that enables developers to test their websites across various browsers on different operating systems and mobile devices, without requiring users to install virtual machines, devices or emulators. BrowserStack and Sauce Labs provide the same services -the difference is in the available amount of devices and configurations.

Watch this video to learn more about how to set up an environment for BrowserStack

To create an environment that points to BrowserStack, please create a BrowserStack account in advance.

Select the Environment type* as Web Only – Browser Stack from the drop-down and then provide the values for the below fields:

mceclip3.png

  1. Specify a unique title for the environment, e.g “BrowserStack_Win10_Chrome”.
  2. BrowserStack account Username must be provided.
  3. BrowserStack account Access Key must be specified.
  4. Choose the desired “Platform & OS” from the available list of the drop-down.
  5. For the specified platform, choose the platform version from the available drop-down list on which testing is required as a part of this environment configuration.
  6. Choose the browser from the available drop-down list on which testing is required as a part of this environment configuration.
  7. The browser version can be specified in case a test has to be executed on a specific browser version. However, in case of version info is not available, “latest” should be chosen as the option.
  8. Leave this unchecked for hosted websites. The Local Identifier should be enabled in case a locally hosted site is to be tested. Local Testing allows you to test your private and internal servers alongside public URLs, using the BrowserStack cloud, which has support for firewalls, proxies, and Active Directory.
  9. Choose the wanted screen resolution used when executing automation flows on the BrowserStack machine.
  10. The description is an optional field which can be used for keeping some notes/description about the environment.

After specifying all values, test the connection by clicking ‘Test connection’. If the environment is set up correctly LEAPWORK will show a ‘Successfully connected’ message in green. 

Web-only GridLastic

Gridlastic is a cloud-based cross-browser testing tool that enables developers to test their websites across various browsers on different operating systems without requiring users to install virtual machines, devices, and operating systems. 

To create an environment that points to Gridlastic, please create a Gridlastic account in advance.

Select the Environment type* as Web Only – Gridlastic from the drop-down and then provide the values for the below fields:

mceclip4.png

  1. Specify a unique title for the environment, e.g “Gridlastic_Win10_Chrome”.
  2. Provide your Gridlastic Subdomain.
  3. Gridlastic Port - the default is 80.
  4. Hub Username must be provided.
  5. Hub Password must be specified.
  6. Choose the desired “Platform & OS” from the available list of the drop-down.
  7. For the specified platform, choose the platform version from the available drop-down list on which testing is required as a part of this environment configuration.
  8. Choose the browser from the available drop-down list on which testing is required as a part of this environment configuration.
  9. The browser version can be specified in case a test has to be executed on a specific browser version. However, if the version information is not available, “latest” should be chosen as the option.
  10. Choose the wanted screen resolution used when executing automation flows on the Gridlastic machine.
  11. The description is an optional field which can be used for keeping some notes/description about the environment.

  12. With the Chrome browser, users can automate web applications on Desktop, Phone, Tablet, and Laptop. Below are the options available under Device type section

    • ‘Desktop’: Use this option to automate web applications on desktop machines
    • ‘Phone, Tablet and Laptop’: Choose any desired option from the drop-down
    • ‘Custom’: Users can define custom devices by specifying width, height, pixel rate, and user-agent. Landscape/Portrait mode setting can be achieved by specifying width, height as per the device.

    Please note that the device type section will be available only when ‘Browser to start’ is set to ‘Chrome’.

After specifying all values, test the connection by clicking ‘Test connection’. If the environment is set up correctly LEAPWORK will show a ‘Successfully connected’ message in green.

Web Only – LambdaTest

LambdaTest is a cloud-based cross-browser testing tool that allows you to perform cross-browser testing for web applications across more than 2000 browsers, operating systems, and devices. You can perform both manual and automated cross browser testing using LambdaTest.

For example, you can test your web application across the most recognized web browsers, such as Chrome, Safari, Firefox, Edge, Internet Explorer, Opera, and Yandex.

Select the Environment type* as Web Only – LambdaTest from the drop-down and then provide the values for below fields:

Untitled.png

  1. Specify a unique title for the environment, e.g “LambdaTest_Win10_Chrome”.
  2. Specify the IP address, machine name, or DNS name for the Hub of LambdaTest.
  3. LambdaTest Port, default is 80.
  4. LambdaTest account Username must be provided.
  5. LambdaTest account Access Key must be specified.
  6. Choose the desired “Platform & OS” from the available list of the drop-down.
  7. For the specified platform, choose the platform version from the available drop-down list on which testing is required as a part of this environment configuration.
  8. Choose the browser from the available drop-down list on which testing is required as a part of this environment configuration.
  9. The browser version can be specified in case a test has to be executed on a specific browser version. However, if version information is not available, “latest” should be chosen as the option.
  10. Choose the wanted screen resolution used when executing automation flows on the LambdaTest machine.
  11. The description is an optional field which can be used for keeping some notes/description about the environment.

After specifying all values, test the connection by clicking ‘Test connection’. If the environment is set up correctly, LEAPWORK will show a ‘Successfully connected’ message in green.

For any clarification, please contact our Priority Support. 

Related articles

Comments

0 comments

Please sign in to leave a comment.