Selenium Grid Test Environments
SELENIUM VERSION V4 |
||||
---|---|---|---|---|
WINDOWS 10 |
||||
platformName | browserName | browserVersion (string) | gridlastic:options - video (boolean) | |
WIN10 | MicrosoftEdge | 99-129, latest |
true or false | |
WIN10 | chrome | 99-129, latest |
true or false | |
WIN10 | firefox | 98-130 | true or false | |
WIN10 | internet explorer | 11.edge-latest, 11.edge-129, 11.edge-128, 11.edge-127, 11.edge-126, 11.edge-125, 11.edge-124, 11.edge-123, 11.edge-122, 11.edge-121, 11.edge-120, 11.edge-119, 11.edge-118, 11.edge-117, 11.edge-116, 11.edge-115, 11.edge-114, 11.edge-113, 11.edge-112, 11.edge-111, 11.edge-110, 11.edge-109, 11.edge-108, 11.edge-107, 11.edge-106, 11.edge-105, 11.edge-104, 11.edge-103, 11.edge-102, 11.edge-101, 11.edge-100 | * | |
LINUX |
||||
platformName | browserName | browserVersion (string) | gridlastic:options - video (boolean) | |
LINUX | MicrosoftEdge | 99-129, latest |
true or false | |
LINUX | chrome | 99-129, latest |
true or false | |
LINUX | firefox | 98-130 | true or false |
* See an example how to enable video recording for internet explorer and Edge IE Mode
SELENIUM VERSION V2/V3 |
||||
---|---|---|---|---|
WINDOWS 10 |
||||
platform (upper case) | browserName (lower case) | version (string) | video (case sensitive string) | |
WIN10 | MicrosoftEdge | 99-129, latest |
"True" or "False" | |
WIN10 | internet explorer | 11 | "True" or "False" | |
WIN10 | chrome | 99-129, latest |
"True" or "False" | |
WIN10 | firefox | 39-130, latest |
"True" or "False" | |
LINUX |
||||
platform (upper case) | browserName (lower case) | version (string) | video (case sensitive string) | |
LINUX | chrome | 99-129, latest |
"True" or "False" | |
LINUX | firefox | 39-130, latest |
"True" or "False" |
MAC OS |
||||
---|---|---|---|---|
Gridlastic uses Amazon EC2 and currently Mac OS instances are not available as regular charged by the minute instances. Instead a lot of our customers use Gridlastic to run 90-95% of their desktop testing using Chrome, Firefox, Edge and Internet Explorer on Windows and Linux at very low cost and high speed, and then only a smaller portion using other browsers locally or with other providers when needed. |
FIREFOX TESTING
You can request a Firefox test environment by setting the browser version to "latest" or by specific version number along with the platform required.
Unlike Chrome, Microsoft Edge and Internet Explorer, Firefox is directly connected to the selenium version, see table of recommendations below:
Selenium Version | Firefox Version | Gecko Driver Version | Notes |
---|---|---|---|
129+ | 0.35.0 | If you are using Selenium V4, testing with Firefox 129 requires you to use Selenium version 4.22.0+. | |
122-128 | 0.34.0 | ||
4.10.0 | Using 4.10.0 and Augmenter the Firefox session will by default try to make BiDi calls which requires BiDi activation with "options.setCapability("webSocketUrl", true)". We support both CDP and BiDi, see Selenium BiDi code example. | ||
4.5.0+ | 112+ | 0.33.0 | |
4.5.0+ | 110-111 | 0.32.2 | |
4.5.0+ | 106-109 | 0.32.0 | |
4.5.0+ | 105 | 0.31.0 | If you are using Selenium V4, Firefox 105 only works with Selenium version 4.5.0+. |
4.1.4+ | 98+ | 0.31.0 | Set browserVersion to an exact Firefox version as in selenium V4 you can not use "latest". |
3.11.0 - 3.14.0 | 80+ | 0.29.0 | Depending on your selenium language client and version, you might have to use the latest W3C standard code and specifically specify the binary location on the node (unless you use version=latest) like:
Java example testing with Firefox 92: FirefoxOptions Options = new FirefoxOptions(); Options.setBinary("/home/ubuntu/Downloads/firefox92/firefox"); // LINUX capabilities.setCapability("moz:firefoxOptions", Options); or Options.setBinary("C:\\Program Files (x86)\\Mozilla Firefox\\firefox92\\firefox.exe"); // WINDOWS Also, when testing on windows you must include the capability "platformName" set to value "windows" otherwise the geckodriver will not accept the request. In addition, you must also include the capability "platform" set to the standard value "WIN10", in order to route your tests to the desired windows environment. See code examples for guidance on your specific selenium language client. Other: If you use a selenium proxy and specify "setSocksProxy" you also have to specify a "setSocksVersion", a W3C standard requirement. |
3.14.0 | 60-79 | 0.23.0 | |
3.12.0 - 3.13.0 | 55-62 | 0.20.1 | |
3.11.0 | 55-62 | 0.20.0 | |
3.9.1 | 55-62 | 0.19.1 | |
3.5.3 | 55-62 | 0.19.1 | |
3.3.1 | 52-54 | Starting with selenium 3.3.1, you cannot test with older firefox versions as only firefox version 52-54 is supported. | |
3.0.1, 3.1, 3.2.0 | <51 | If you use selenium version 3.01, 3.1 or 3.2, then you can still test older Firefox even if you run selenium 3. To do this specify the capability "marionette" set to false in your test script whenever you want to test a Firefox version below 48. This will bypass the geckodriver and use the original selenium firefox driver. |
Firefox 47: only works with selenium version 2.53.1
Firefox 46: 2.53.0, 2.53.1
Firefox 39 - 45: 2.53.0
CHROME TESTING
You can request a Chrome test environment by setting the browser version to "latest" or by specific version number along with the platform required.
Please note that if you test with many different browsers and have limited grid max nodes, we recommend that you always asks for browser version ”latest”, which will give you a test environment VM with the latest Chrome, Firefox and Microsoft Edge.
Choosing a specific chrome version insulates you from any new changes made to the Chrome browser/Chrome driver that might effect your tests. A new Chrome version is released about every 6 weeks and becomes the "latest" Chrome browser on our main nodes containing multiple browsers.
Chrome is not updated automatically on the grid VM's when a new version is released by Google. Instead we do extensive testing and chromedriver matching before implementing and if it is not found stable enough we hold off until it is. Each Chrome version will use the chromedriver effective when it was initially supported by Gridlastic, see mapping below:
Chrome Version | Chromedriver Version | Notes |
---|---|---|
129, latest | 129.0.6668.58 | |
128 | 128.0.6613.113 | |
127 | 127.0.6533.72 | |
126 | 126.0.6478.114 | |
125 | 125.0.6422.61 | |
124 | 124.0.2478.67 | |
123 | 123.0.6312.86 | |
122 | 122.0.6261.69 | |
121 | 121.0.6167.85 | |
120 | 120.0.6099.71 | |
119 | 119.0.6045.105 | |
118 | 118.0.5993.88 | |
117 | 117.0.5938.92 | |
116 | 116.0.5845.110 | |
115 | 115.0.5790.110 | |
114 | 114.0.5735.90 | |
113 | 113.0.5672.63 | |
112 | 112.0.5615.49 | |
111 | 111.0.5563.64 | For Selenium V4 users, starting with Chrome 111 you must either use version 4.8.2 or add options.addArguments("--remote-allow-origins=*"); in order to test with Chrome. |
110 | 110.0.5481.77 | For Selenium V4 starting with Chrome 110 the method for using headless have changed and you must instead use options.addArguments("--headless=new"); |
109 | 109.0.5414.74 | |
108 | 108.0.5359.71 | |
107 | 107.0.5304.62 | |
106 | 106.0.5249.61 | |
105 | 105.0.5195.52 | |
104 | 104.0.5112.79 | |
103 | 103.0.5060.53 | |
102 | 102.0.5005.61 | |
101 | 101.0.4951.41 | |
100 | 100.0.4896.60 | |
99 | 99.0.4844.51 |
MICROSOFT EDGE TESTING
You can request a Microsoft Edge test environment by setting the browser version to "latest" or by specific version number along with the platform required.
Microsoft Edge is not updated automatically on the grid VM's when a new version is released by Microsoft. Instead we do extensive testing and Microsoft Edge Driver matching before implementing and if it is not found stable enough we hold off until it is. Each Microsoft Edge version will use the Microsoft Edge Driver effective when it was initially supported by Gridlastic, see mapping below:
Microsoft Edge Version | Microsoft Edge Driver Version | Internet Explorer Driver (Edge IE11 Mode) | Notes |
---|---|---|---|
129, latest | 129.0.2792.52 | 4.14.0.0 | |
128 | 128.0.2739.54 | 4.14.0.0 | |
127 | 127.0.2651.74 | 4.14.0.0 | |
126 | 126.0.2592.68 | 4.14.0.0 | |
125 | 125.0.2535.51 | 4.14.0.0 | |
124 | 124.0.6367.92 | 4.14.0.0 | |
123 | 123.0.2420.65 | 4.14.0.0 | |
122 | 122.0.2365.52 | 4.14.0.0 | |
121 | 121.0.2277.83 | 4.14.0.0 | |
120 | 120.0.2210.61 | 4.14.0.0 | |
119 | 119.0.2151.44 | 4.14.0.0 | |
118 | 118.0.2088.57 | 4.14.0.0 | Note: because of a bug when testing on Linux you need to specify binary location, options.setBinary("/usr/bin/microsoft-edge"); |
117 | 117.0.2045.43 | 4.11.0.0 | Note: because of a bug when testing on Linux you need to specify binary location, options.setBinary("/usr/bin/microsoft-edge"); |
116 | 115.0.1901.183 | 4.11.0.0 | Note: because of a bug when testing on Linux you need to specify binary location, options.setBinary("/usr/bin/microsoft-edge"); |
115 | 115.0.1901.183 | 4.11.0.0 | |
114 | 114.0.1823.18 | 4.10.0.0 | Starting from Edge 114 there is a "Personalize your web experience" prompt that randomly activates and might effect your test. This prompt can be removed by passing in the argument "--guest". See example code how to disable the Edge Personalize your web experience prompt. |
113 | 113.0.1774.9 | 4.8.1.0 | |
112 | 112.0.1722.34 | 4.8.1.0 | |
111 | 111.0.1661.43 | 4.8.1.0 | |
110 | 110.0.1587.46 | 4.8.0.0 | |
109 | 109.0.1518.52 | 4.8.0.0 | |
108 | 108.0.1462.42 | 4.7.0.0 | |
107 | 107.0.1418.26 | 4.5.0.0 | |
106 | 106.0.1370.37 | 4.5.0.0 | |
105 | 105.0.1343.33 | 4.3.0.0 | |
104 | 104.0.1293.47 | 4.3.0.0 | |
103 | 103.0.1264.37 | 4.2.0.0 | |
102 | 102.0.1245.30 | 4.2.0.0 | |
101 | 101.0.1210.32 | 4.0.0.0 | |
100 | 100.0.1185.39 | 4.0.0.0 | |
99 | 99.0.1150.39 |
INTERNET EXPLORER TESTING
Selenium Version | Notes |
---|---|
4.1.4+ | To continue testing applications requiring internet explorer use Microsoft Edge Internet Explorer mode. Do so by specifying:
InternetExplorerOptions options = new InternetExplorerOptions(); options.attachToEdgeChrome(); options.withEdgeExecutablePath("C:/Program Files (x86)/Microsoft/Edge/Application/msedge.exe"); If you do not enable IE mode the test is carried out on regular internet explorer 11. IE mode is using the Internet explorer driver IEDriverServer.exe which is linked to the Microsoft Edge version installed on the node, see Microsoft Edge testing. You can set the browserVersion=11.edge-latest to test with the latest edge and internet explorer driver. See an edge IE mode example. Video recording of internet explorer tests are enabled by default starting with selenium grid version 4.5.2. |
3.9.1 - 3.14.0 | When testing on windows you must include the capability "platformName" set to value "windows" otherwise the IE driver will not accept the request. In addition, you must also include the capability "platform" set to the standard value "WIN10", in order to route your tests to the desired windows environment. |
SELENIUM VERSIONS
4.25.0
4.24.0
4.23.0
4.22.0
4.21.0
4.20.0
4.19.0
4.18.1
4.17.0
4.16.0
4.15.0
4.14.1
4.13.0
4.12.1
4.11.0
4.10.0
4.9.1
4.8.3
4.8.2
4.8.1
4.8.0 (From this version downloading files from grid nodes are supported for Chrome, Firefox and Edge, see selenium download files examples)
4.7.0
4.6.0
4.5.2
4.4.0
4.3.0
4.2.1
4.1.4
3.14.0
3.13.0
3.12.0
3.11.0
3.9.1
3.5.3
3.3.1
3.2.0
3.1.0
3.0.1
2.53.1
2.53.0
Note: we do extensive testing of the remote selenium grid functionality for each new selenium release and only support stable enough versions.
EC2 REGIONS
Launch your selenium grid in any of these Amazon Regions. You can change in which region to launch your selenium grid at anytime.
AWS EC2 Region | Selenium Version Support |
---|---|
US East (N. Virginia) us-east-1 | V2, V3, V4 |
US East (Ohio) us-east-2 | V2, V3, V4 |
US West (N. California) us-west-1 | V2, V3, V4 |
US West (Oregon) us-west-2 | V2, V3, V4 |
Asia Pacific (Hong Kong) ap-east-1 | V4 |
Asia Pacific (Mumbai) ap-south-1 | V2, V3, V4 |
Asia Pacific (Singapore) ap-southeast-1 | V4 |
Asia Pacific (Sydney) ap-southeast-2 | V4 |
Canada (Central) ca-central-1 | V2, V3, V4 |
Europe (Frankfurt) eu-central-1 | V2, V3, V4 |
Europe (Ireland) eu-west-1 | V2, V3, V4 |
Europe (London) eu-west-2 | V2, V3, V4 |
Europe (Milan) eu-south-1 | V4 |
Europe (Paris) eu-west-3 | V4 |
Europe (Stockholm) eu-north-1 | V4 |
South America (São Paulo) sa-east-1 | V4 |
SCREEN RESOLUTIONS
You can test with any screen size you like using Chrome headless mode like:
ChromeOptions options = new ChromeOptions();
options.addArguments("headless"); // Note: for Selenium V4 starting with Chrome 110 instead use options.addArguments("--headless=new")
options.addArguments("window-size=2560x1440");
For fast headless Chrome testing do not enable test video recording as it is not available in this mode. Otherwise the maximum screen size is 1920x1080 (node size c5.large+) and 1280x1024 (node size c4.large) on Windows and 1920x1080 on Linux. See code examples how to change the window size.
VIDEO RECORDING OF TESTS
Video recording is disabled by default. Enable by passing in the capability "video" set to "True" (Selenium version V2/V3) or gridlastic:options "video" set to "true" (Selenium version V4) and then access the videos via the selenium session id, see selenium grid code examples
Video captures screen size 1920x1080 (node size c5.large+) and 1280x1024 (node size c4.large) on Windows and 1920x1080 on Linux with a max video recording time of 40 minutes (there is no limit how long your test run but the video recording stops at 40 minutes and does not effect the test).
NOTES:
Gridlastic auto scaling requires all 3 test environment parameters platform, browser and browser version to be specified in order to launch selenium grid nodes to fulfill test demand.
See how to request these test environments in selenium grid code examples
Try our
SELENIUM GRID DEMO