Gridlastic Selenium Grid Configuration Parameters

All your selenium grid configurations is done in a single place at the "Grid Configuration" page in the Gridlastic dashboard. After the selenium grid is launched, your grid access credentials will be displayed.


Gridlastic Grid Configuration Start Page

Click image to enlarge.



Subdomain

Enter your Gridlastic selenium grid subdomain.


EC2 Region

Select in which Amazon EC2 Data Region to launch the grid.

Options:
US East (Northern Virginia)
US East (Ohio)
US West (Oregon)
US West (Northern California)
EU (Ireland)
EU (Frankfurt)
EU (London)
Canada (Central)
Asia Pacific (Singapore)
Asia Pacific (Sydney)
Asia Pacific (Tokyo)
Asia Pacific (Seoul)
Asia Pacific (Mumbai)
South America (Sao Paulo)


Selenium Version

Select the selenium version you want to use for your grid. You should use the same selenium client version locally to avoid unexpected results. Note: for firefox testing please see our test environment docs for guidance of which selenium version would be best suited for your needs.


Node Type

Grid nodes can either be requested as On-Demand or as Spot (recommended). On-Demand nodes launches a little bit faster than spot nodes, but spot nodes cost way less, up to 90% off regular Amazon price! Nearly all of our customers use spot nodes for their grid.

Options: On-Demand or Spot


Node Size

Specify machine size for your grid nodes, the larger/faster machine the higher cost. You might have to experiment with what machine size works best for your type of testing. If you have a light web site to test and do not video record your tests, m1.small could work for you. If you plan to video record your tests with higher quality or simply want more speed/memory, we recommend c4.large.

Options: m1.small, c3.large and c4.large


Spot Max Wait Time

Only if node type spot is selected. Time in minutes before an unfulfilled spot request is canceled and replaced by an On-Demand request. Note: average spot request wait time is only about 30 seconds and only in very rare cases does the wait time for a spot request exceed 10 minutes. Recommended setting is 10 minutes.


Windows Node Termination Schedule

Grid nodes that are not busy processing tests will be terminated according to the node termination schedule selected. Windows instances are charged by Amazon AWS by the hour so you must select an hourly termination schedule. NOTE: selecting a shorter schedule could reduce the time that a node is running idle and could result in less usage. Selecting a longer schedule would increase node availability and minimize test start times. Please note that it can take 5-7 minutes for a windows node to be launched and this time is included in the total billed time of the node. Minimum billed time for a windows node is 1 hour.

Options:
Hourly - first attempt at 1:st hour
Hourly - first attempt at 2:nd hour
Hourly - first attempt at 3:rd hour
Hourly - first attempt at 4:th hour


Linux Node Termination Schedule

Grid nodes that are not busy processing tests will be terminated according to the node termination schedule selected. Linux instances are charged by Amazon AWS for part use of an hour so you can select a termination schedule less than 1 hour if you want. NOTE: selecting a shorter schedule could reduce the time that a node is running idle and could result in less usage. Selecting a longer schedule would increase node availability and minimize test start times. Please note that it can take 2-4 minutes for a Linux node to be launched and this time is included in the total billed time of the node. Minimum billed time for a Linux node is 15 minutes.

Options:
Every 15 minutes
Every 30 minutes
Hourly - first attempt at 1:st hour
Hourly - first attempt at 2:nd hour
Hourly - first attempt at 3:rd hour
Hourly - first attempt at 4:th hour


Node Timezone

Select timezone for your grid nodes or leave as UTC time (Coordinated Universal Time). Linux timezones are approximated.


Max Concurrent Nodes

Maximum nodes registered to the grid hub server at any time. 1 node = 1 VM machine running 1 browser session at the time (read more about why we do this). A node have multiple browsers and browser versions installed.


Selenium Grid Timeout

Shorter time increases sensitivity to slow network connections and could result in increased test timeouts.

Options: 1-10 minutes


Days to Keep Video Files

Number of days video files are kept in our system before deleted. If you want to keep your video files for longer than 180 days you can easily download them manually or programmatically and store locally.

Options: 1-180 days


Optional. Restrict source IP access to selenium grid hub (port 80, 4444)

Optional. Want to improve user access security for your organization beyond usernames and passwords? You can further restrict access to your selenium grid hub to just internal company traffic by specifying your corporate public IP address range (ask your network administrator for this range in CIDR format) and/or specific IP addresses of servers like Jenkins located elsewhere from where you run your test scripts. Specify CIDR(S) like 50.16.0.0/15, 50.19.0.0/16. To specify access for single IP addresses use suffix /32, like xxx.xxx.xxx.xxx/32. To allow all IP addresses leave empty. Use commas to add multiple CIDR(S). Max 50 entries. By default, access to your selenium grid hub also requires a username/password that is displayed when your grid is launched.


Optional. Enable Gridlastic Connect (port 443)

Optional. Enable Gridlastic Connect, see documentation about Gridlastic Connect encrypted tunneling solution. By default Gridlastic Connect is disabled and port 443 is closed to all IP addresses. To enable Gridlastic Connect, you must specify the public source IP addresses from where your Gridlastic Connect tunnel client(s) will connect from. Allow connections from just internal company traffic by specifying your corporate public IP range (ask your network administrator for this range in CIDR format) and/or specific IP addresses of machines located elsewhere from where the tunnel client connects from. Specify CIDR(S) like 50.16.0.0/15, 50.19.0.0/16. To specify access for single IP addresses use suffix /32, like xxx.xxx.xxx.xxx/32. Use commas to add multiple CIDR(S). Max 50 entries. In addition to IP access restrictions, Gridlastic Connect requires the same username/password as your selenium grid hub.


Re-Generate Hub Username and Password

If selected, the username and password for the hub will be re-generated.





Gridlastic Grid Configuration Page - your selenium grid is running and grid credentials are displayed

Click image to enlarge.



Subdomain

Your Gridlastic selenium grid subdomain.


Hub Username/Password

Basic http username/password for your Selenium Grid Hub. You have the option to re-generate this value upon launching a new grid. If a grid is running you must first terminate the grid to change any grid configurations.


API endpoint with hub username and password

Your selenium grid hub http endpoint with username and password. Use port 80 or 4444. This is the hub endpoint you reference in your selenium test scripts, see selenium grid examples in documentation. Note: you can also use Gridlastic Connect to access your selenium grid hub via an encrypted tunnel.


Video Files Location Endpoint

Access and play your test video files at this location. This location will change depending in what Amazon data region your grid is launched. If video recording is requested, videos can be immediately played after each test completes via the selenium session id. See selenium grid code examples in documentation how to implement video links into your test scripts. Videos can be accessed via http or https.


Hub Proxy Static IP

Your selenium grid hub also hosts a Squid non caching proxy on port 8001 and you can choose to route your grid nodes traffic via this proxy. The advantage is that your grid nodes browser traffic will come from a single static IP that is unique for your account and you can whitelist this IP to give access to your protected web servers. See documentation how to implement selenium grid proxy routing. NOTE: For free accounts, the proxy IP changes after each grid start.


Hub Console

Click this link(s) to access your selenium grid hub console using your hub username and hub password. See your grid at work!