Selenium

Browsing Context

Mon, 01 Jan 0001 00:00:00 +0000

Commands

This section contains the APIs related to browsing context commands.

Open a new window

Creates a new browsing context in a new window.

 Assertions.assertEquals(id, browsingContext.getId());
 }

 @Test

View Complete Code View on GitHub

Add Example

Captchas

Mon, 01 Jan 0001 00:00:00 +0000

CAPTCHA, short for Completely Automated Public Turing test to tell Computers and Humans Apart, is explicitly designed to prevent automation, so do not try! There are two primary strategies to get around CAPTCHA checks:

Disable CAPTCHAs in your test environment
Add a hook to allow tests to bypass the CAPTCHA

Selenium components

Mon, 01 Jan 0001 00:00:00 +0000

Building a test suite using WebDriver will require you to understand and effectively use several components. As with everything in software, different people use different terms for the same idea. Below is a breakdown of how terms are used in this description.

Terminology

API: Application Programming Interface. This is the set of “commands” you use to manipulate WebDriver.
Library: A code module that contains the APIs and the code necessary to implement them. Libraries are specific to each language binding, eg .jar files for Java, .dll files for .NET, etc.
Driver: Responsible for controlling the actual browser. Most drivers are created by the browser vendors themselves. Drivers are generally executable modules that run on the system with the browser itself, not the system executing the test suite. (Although those may be the same system.) NOTE: Some people refer to the drivers as proxies.
Framework: An additional library that is used as a support for WebDriver suites. These frameworks may be test frameworks such as JUnit or NUnit. They may also be frameworks supporting natural language features such as Cucumber or Robot Framework. Frameworks may also be written and used for tasks such as manipulating or configuring the system under test, data creation, test oracles, etc.

The Parts and Pieces

At its minimum, WebDriver talks to a browser through a driver. Communication is two-way: WebDriver passes commands to the browser through the driver, and receives information back via the same route.

Copyright and attributions

Mon, 01 Jan 0001 00:00:00 +0000

The Documentation of Selenium

Every effort has been made to make this documentation as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as-is” basis. The authors and the publisher shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained herein. No patent liability is assumed with respect to the use of the information contained herein.

Design patterns and development strategies

Mon, 01 Jan 0001 00:00:00 +0000

(previously located: https://github.com/SeleniumHQ/selenium/wiki/Bot-Style-Tests)

Overview

Over time, projects tend to accumulate large numbers of tests. As the total number of tests increases, it becomes harder to make changes to the codebase — a single “simple” change may cause numerous tests to fail, even though the application still works properly. Sometimes these problems are unavoidable, but when they do occur you want to be up and running again as quickly as possible. The following design patterns and strategies have been used before with WebDriver to help make tests easier to write and maintain. They may help you too.

Waiting with Expected Conditions

Mon, 01 Jan 0001 00:00:00 +0000

Expected Conditions are used with Explicit Waits. Instead of defining the block of code to be executed with a lambda, an expected conditions method can be created to represent common things that get waited on. Some methods take locators as arguments, others take elements as arguments.

These methods can include conditions such as:

element exists
element is stale
element is visible
text is visible
title contains specified value

Expected Conditions Documentation

Configuration help

Mon, 01 Jan 0001 00:00:00 +0000

The help commands display information based on the current code implementation. Hence, it will provide accurate information in case the documentation is not updated. It is the easiest way to learn about Grid 4 configuration for any new version.

Info Command

The info command provides detailed docs on the following topics:

Configuring Selenium
Security
Session Map setup
Tracing

Config help

Quick config help and overview is provided by running:

Input

Mon, 01 Jan 0001 00:00:00 +0000

This section contains the APIs related to input commands.

Perform Actions

Selenium v4.17

 Actions selectThreeOptions =
 actions.click(options.get(1)).keyDown(Keys.SHIFT).click(options.get(3)).keyUp(Keys.SHIFT);

 input.perform(windowHandle, selectThreeOptions.getSequences());

View Complete Code View on GitHub

Add Example

Locator strategies

Mon, 01 Jan 0001 00:00:00 +0000

A locator is a way to identify elements on a page. It is the argument passed to the Finding element methods.

Check out our encouraged test practices for tips on locators, including which to use when and why to declare locators separately from the finding methods.

Traditional Locators

Selenium provides support for these 8 traditional location strategies in WebDriver:

Locator	Description
class name	Locates elements whose class name contains the search value (compound class names are not permitted)
css selector	Locates elements matching a CSS selector
id	Locates elements whose ID attribute matches the search value
name	Locates elements whose NAME attribute matches the search value
link text	Locates anchor elements whose visible text matches the search value
partial link text	Locates anchor elements whose visible text contains the search value. If multiple elements are matching, only the first one will be selected.
tag name	Locates elements whose tag name matches the search value
xpath	Locates elements matching an XPath expression

Creating Locators

To work on a web element using Selenium, we need to first locate it on the web page. Selenium provides us above mentioned ways, using which we can locate element on the page. To understand and create locator we will use the following HTML snippet.

Log

Mon, 01 Jan 0001 00:00:00 +0000

This section contains the APIs related to logging.

Console logs

Listen to the console.log events and register callbacks to process the event.

Selenium v4.8

 CompletableFuture<ConsoleLogEntry> future = new CompletableFuture<>();
 logInspector.onConsoleEntry(future::complete);

 driver.get("https://www.selenium.dev/selenium/web/bidi/logEntryAdded.html");
 driver.findElement(By.id("consoleLog")).click();

 ConsoleLogEntry logEntry = future.get(5, TimeUnit.SECONDS);

View Complete Code View on GitHub

Add Example

WebDriver BiDi Logging Features

Mon, 01 Jan 0001 00:00:00 +0000

Remember that to use WebDriver BiDi, you must enable it in Options. For more details, see Enabling BiDi

Console Message Handlers

Record or take actions on console.log events.

Add Handler

Implementation Missing

Browser navigation

Mon, 01 Jan 0001 00:00:00 +0000

Navigate to

The first thing you will want to do after launching a browser is to open your website. This can be achieved in a single line:

 //Convenient
 driver.get("https://selenium.dev");
 
 //Longer way
 driver.navigate().to("https://selenium.dev");

View Complete Code View on GitHub

driver.get("https://www.selenium.dev/selenium/web/index.html")

View Complete Code View on GitHub

 //Convenient
 driver.Url = "https://selenium.dev";
 //Longer
 driver.Navigate().GoToUrl("https://selenium.dev");

View Complete Code View on GitHub


 it 'navigates to a page' do
 driver.navigate.to 'https://www.selenium.dev/'

View Complete Code View on GitHub

 //Convenient
  await driver.get('https://www.selenium.dev');
 
  //Longer way
  await driver.navigate().to("https://www.selenium.dev/selenium/web/index.html");

View Complete Code View on GitHub

//Convenient
driver.get("https://selenium.dev")

//Longer way
driver.navigate().to("https://selenium.dev")

Back

Pressing the browser’s back button:

WebDriver BiDi Network Features

Mon, 01 Jan 0001 00:00:00 +0000

The implementation of these features is being tracked here: #13993

Remember that to use WebDriver BiDi, you must enable it in Options. For more details, see Enabling BiDi

Authentication Handlers

Authentication handlers enable you to intercept authentication requests that occur during a network interaction. These handlers are useful for automating scenarios involving authentication prompts, such as Basic Auth or Digest Auth. They allow you to programmatically provide credentials or modify the authentication flow.

Network

Mon, 01 Jan 0001 00:00:00 +0000

Commands

This section contains the APIs related to network commands.

Add network intercept

Selenium v4.18

 String intercept =
 network.addIntercept(new AddInterceptParameters(InterceptPhase.BEFORE_REQUEST_SENT));
 Assertions.assertNotNull(intercept);

View Complete Code View on GitHub

Add Example

Observability in Selenium Grid

Mon, 01 Jan 0001 00:00:00 +0000

Selenium Grid

Grid aids in scaling and distributing tests by executing tests on various browser and operating system combinations.

Observability

Observability has three pillars: traces, metrics and logs. Since Selenium Grid 4 is designed to be fully distributed, observability will make it easier to understand and debug the internals.

Distributed tracing

A single request or transaction spans multiple services and components. Tracing tracks the request lifecycle as each service executes the request. It is useful in debugging in an error scenario. Some key terms used in tracing context are:

Overview of Test Automation

Mon, 01 Jan 0001 00:00:00 +0000

First, start by asking yourself whether or not you really need to use a browser. Odds are that, at some point, if you are working on a complex web application, you will need to open a browser and actually test it.

Functional end-user tests such as Selenium tests are expensive to run, however. Furthermore, they typically require substantial infrastructure to be in place to be run effectively. It is a good rule to always ask yourself if what you want to test can be done using more lightweight test approaches such as unit tests or with a lower-level approach.

WebDriver BiDi Script Features

Mon, 01 Jan 0001 00:00:00 +0000

The implementation of these features is being tracked here: #13992

Remember that to use WebDriver BiDi, you must enable it in Options. For more details, see Enabling BiDi

Script Pinning

Execute Script

DOM Mutation Handlers

Script

Mon, 01 Jan 0001 00:00:00 +0000

Commands

This section contains the APIs related to script commands.

Call function in a browsing context

Selenium v4.15

 try (Script script = new Script(id, driver)) {
 List<LocalValue> arguments = new ArrayList<>();
 arguments.add(PrimitiveProtocolValue.numberValue(22));

 Map<Object, LocalValue> value = new HashMap<>();
 value.put("some_property", LocalValue.numberValue(42));
 LocalValue thisParameter = LocalValue.objectValue(value);

 arguments.add(thisParameter);

 EvaluateResult result =
 script.callFunctionInBrowsingContext(
 id,
 "function processWithPromise(argument) {\n"
 + " return new Promise((resolve, reject) => {\n"
 + " setTimeout(() => {\n"
 + " resolve(argument + this.some_property);\n"
 + " }, 1000)\n"
 + " })\n"
 + "}",
 true,
 Optional.of(arguments),
 Optional.of(thisParameter),
 Optional.of(ResultOwnership.ROOT));

View Complete Code View on GitHub

Add Example

JavaScript alerts, prompts and confirmations

Mon, 01 Jan 0001 00:00:00 +0000

WebDriver provides an API for working with the three types of native popup messages offered by JavaScript. These popups are styled by the browser and offer limited customisation.

Alerts

The simplest of these is referred to as an alert, which shows a custom message, and a single button which dismisses the alert, labelled in most browsers as OK. It can also be dismissed in most browsers by pressing the close button, but this will always do the same thing as the OK button. See an example alert.

CLI options in the Selenium Grid

Mon, 01 Jan 0001 00:00:00 +0000

Different sections are available to configure a Grid. Each section has options can be configured through command line arguments.

A complete description of the component to section mapping can be seen below.

Note that this documentation could be outdated if an option was modified or added but has not been documented yet. In case you bump into this situation, please check the “Config help” section and feel free to send us a pull request updating this page.

Contributing to the Selenium site & documentation

Mon, 01 Jan 0001 00:00:00 +0000

Selenium is a big software project, its site and documentation are key to understanding how things work and learning effective ways to exploit its potential.

This project contains both Selenium’s site and documentation. This is an ongoing effort (not targeted at any specific release) to provide updated information on how to use Selenium effectively, how to get involved and how to contribute to Selenium.

Contributions toward the site and docs follow the process described in the below section about contributions.

Crazy Fun Build Tool

Mon, 01 Jan 0001 00:00:00 +0000

This documentation previously located on the wiki

WebDriver is a large project: if we tried to push everything into a single monolithic build file it eventually becomes unmanageable. We know this. We’ve tried it. So we broke the single Rakefile into a series of build.desc files. Each of these describe a part of the build.

Let’s take a look at a build.desc file. This is part of the main test build.desc:

java_test(name = "single",
 srcs = [
 "SingleTestSuite.java",
 ],
 deps = [
 ":tests",
 "//java/server/src/org/openqa/selenium/server",
 "//java/client/test/org/openqa/selenium/v1:selenium-backed-webdriver-test",
 "//java/client/test/org/openqa/selenium/firefox:test",
 ] ])

Targets

This highlights most of the key concepts. Firstly, it declares target, in this case there is a single java_test target. Each target has a name attribute.

A deeper look at Selenium

Mon, 01 Jan 0001 00:00:00 +0000

Selenium controls web browsers

Selenium is many things but at its core, it is a toolset for web browser automation that uses the best techniques available to remotely control browser instances and emulate a user’s interaction with the browser.

Selenium allows users to simulate common activities performed by end-users; entering text into fields, selecting drop-down values and checking boxes, and clicking links in documents. It also provides many other controls such as mouse movement, arbitrary JavaScript execution, and much more.

File downloads

Mon, 01 Jan 0001 00:00:00 +0000

Whilst it is possible to start a download by clicking a link with a browser under Selenium’s control, the API does not expose download progress, making it less than ideal for testing downloaded files. This is because downloading files is not considered an important aspect of emulating user interaction with the web platform. Instead, find the link using Selenium (and any required cookies) and pass it to a HTTP request library like curl.

Finding web elements

Mon, 01 Jan 0001 00:00:00 +0000

One of the most fundamental aspects of using Selenium is obtaining element references to work with. Selenium offers a number of built-in locator strategies to uniquely identify an element. There are many ways to use the locators in very advanced scenarios. For the purposes of this documentation, let’s consider this HTML snippet:

<ol id="vegetables">
 <li class="potatoes">…
 <li class="onions">…
 <li class="tomatoes"><span>Tomato is a Vegetable</span>…
</ol>
<ul id="fruits">
 <li class="bananas">…
 <li class="apples">…
 <li class="tomatoes"><span>Tomato is a Fruit</span>…
</ul>

First matching element

Many locators will match multiple elements on the page. The singular find element method will return a reference to the first element found within a given context.

Getting started with Selenium Grid

Mon, 01 Jan 0001 00:00:00 +0000

Quick start

Prerequisites
- Java 11 or higher installed
- Browser(s) installed
- Browser driver(s)
  - Selenium Manager will configure the drivers automatically if you add --selenium-manager true.
  - Installed and on the PATH
- Download the Selenium Server jar file from the latest release
Start the Grid
- java -jar selenium-server-<version>.jar standalone
Point* your WebDriver tests to http://localhost:4444
(Optional) Check running tests and available capabilities by opening your browser at http://localhost:4444

*Wondering how to point your tests to http://localhost:4444? Check the RemoteWebDriver section.

GraphQL query support

Mon, 01 Jan 0001 00:00:00 +0000

GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. It gives users the power to ask for exactly what they need and nothing more.

Enums

Enums represent possible sets of values for a field.

For example, the Node object has a field called status. The state is an enum (specifically, of type Status) because it may be UP , DRAINING or UNAVAILABLE.

Grid 3

Mon, 01 Jan 0001 00:00:00 +0000

You can read our documentation for more information about Grid 4

Selenium Grid is a smart proxy server that allows Selenium tests to route commands to remote web browser instances. Its aim is to provide an easy way to run tests in parallel on multiple machines.

With Selenium Grid, one server acts as the hub that routes JSON formatted test commands to one or more registered Grid nodes. Tests contact the hub to obtain access to remote browser instances. The hub has a list of registered servers that it provides access to, and allows control of these instances.

HTML runner

Mon, 01 Jan 0001 00:00:00 +0000

Selenium HTML-runner allows you to run Test Suites from a command line. Test Suites are HTML exports from Selenium IDE or compatible tools.

Common information

Combination of releases of geckodriver / firefox / selenium-html-runner matters. There might be a software compatibility matrix somewhere.
selenium-html-runner runs only Test Suite (not Test Case - for example an export from Monitis Transaction Monitor). Be sure you comply with this.
For Linux users with no DISPLAY - you need to start html-runner with Virtual display (search for xvfb)

Example Linux environment

Install / download following software packages:

Install a Selenium library

Mon, 01 Jan 0001 00:00:00 +0000

First you need to install the Selenium bindings for your automation project. The installation process for libraries depends on the language you choose to use. Make sure you check the Selenium downloads page to make sure you are using the latest version.

Requirements by language

View the minimum supported Java version here.

Interacting with web elements

Mon, 01 Jan 0001 00:00:00 +0000

There are only 5 basic commands that can be executed on an element:

click (applies to any element)
send keys (only applies to text fields and keyboard interactable elements)
clear (only applies to text fields and content editable elements)
submit (only applies to form elements)
select (see Select List Elements)

Additional validations

These methods are designed to closely emulate a user’s experience, so, unlike the Actions API, it attempts to perform two things before attempting the specified action.

Internet Explorer Driver Internals

Mon, 01 Jan 0001 00:00:00 +0000

Client Code Into the Driver

We use the W3C WebDriver protocol to communicate with a local instance of an HTTP server. This greatly simplifies the implementation of the language-specific code, and minimzes the number of entry points into the C++ DLL that must be called using a native-code interop technology such as JNA, ctypes, pinvoke or DL.

Memory Management

The IE driver utilizes the Active Template Library (ATL) to take advantage of its implementation of smart pointers to COM objects. This makes reference counting and cleanup of COM objects much easier.

Keyboard actions

Mon, 01 Jan 0001 00:00:00 +0000

There are only 2 actions that can be accomplished with a keyboard: pressing down on a key, and releasing a pressed key. In addition to supporting ASCII characters, each keyboard key has a representation that can be pressed or released in designated sequences.

Keys

In addition to the keys represented by regular unicode, unicode values have been assigned to other keyboard keys for use with Selenium. Each language has its own way to reference these keys; the full list can be found here.

Command Listeners

Mon, 01 Jan 0001 00:00:00 +0000

These allow you to execute custom actions in every time specific Selenium commands are sent

Add Example

Chrome DevTools Logging Features

Mon, 01 Jan 0001 00:00:00 +0000

While Selenium 4 provides direct access to the Chrome DevTools Protocol, these methods will eventually be removed when WebDriver BiDi implemented.

Console Logs

 ((HasLogEvents) driver).onLogEvent(consoleEvent(e -> messages.add(e.getMessages().get(0))));

View Complete Code View on GitHub

 async with driver.bidi_connection() as session:
 async with Log(driver, session).add_listener(Console.ALL) as messages:

View Complete Code View on GitHub

 using IJavaScriptEngine monitor = new JavaScriptEngine(driver);
 var messages = new List<string>();
 monitor.JavaScriptConsoleApiCalled += (_, e) =>
 {
 messages.Add(e.MessageContent);
 };
 await monitor.StartEventMonitoring();

View Complete Code View on GitHub

 driver.on_log_event(:console) { |log| logs << log.args.first }

View Complete Code View on GitHub

Implementation Missing

Browser Options

Mon, 01 Jan 0001 00:00:00 +0000

In Selenium 3, capabilities were defined in a session by using Desired Capabilities classes. As of Selenium 4, you must use the browser options classes. For remote driver sessions, a browser options instance is required as it determines which browser will be used.

These options are described in the w3c specification for Capabilities.

Each browser has custom options that may be defined in addition to the ones defined in the specification.

browserName

Browser name is set by default when using an Options class instance.

Selenium RC (Selenium 1)

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Selenium RC was the main Selenium project for a long time, before the WebDriver/Selenium merge brought up Selenium 2, a more powerful tool. It is worth to highlight that Selenium 1 is not supported anymore.

How Selenium RC Works

First, we will describe how the components of Selenium RC operate and the role each plays in running your test scripts.

RC Components

Selenium RC components are:

The Selenium Server which launches and kills browsers, interprets and runs the Selenese commands passed from the test program, and acts as an HTTP proxy, intercepting and verifying HTTP messages passed between the browser and the AUT.
Client libraries which provide the interface between each programming language and the Selenium RC Server.

Here is a simplified architecture diagram:

Types of Testing

Mon, 01 Jan 0001 00:00:00 +0000

Acceptance testing

This type of testing is done to determine if a feature or system meets the customer expectations and requirements. This type of testing generally involves the customer’s cooperation or feedback, being a validation activity that answers the question:

Are we building the right product?

For web applications, the automation of this testing can be done directly with Selenium by simulating user expected behaviour. This simulation could be done by record/playback or through the different supported languages as explained in this documentation. Note: Acceptance testing is a subtype of functional testing, which some people might also refer to.

Migrating from RC to WebDriver

Mon, 01 Jan 0001 00:00:00 +0000

How to Migrate to Selenium WebDriver

A common question when adopting Selenium 2 is what’s the correct thing to do when adding new tests to an existing set of tests? Users who are new to the framework can begin by using the new WebDriver APIs for writing their tests. But what of users who already have suites of existing tests? This guide is designed to demonstrate how to migrate your existing tests to the new APIs, allowing all new tests to be written using the new features offered by WebDriver.

Working With Colors

Mon, 01 Jan 0001 00:00:00 +0000

You will occasionally want to validate the colour of something as part of your tests; the problem is that colour definitions on the web are not constant. Would it not be nice if there was an easy way to compare a HEX representation of a colour with a RGB representation of a colour, or a RGBA representation of a colour with a HSLA representation of a colour?

Worry not. There is a solution: the Color class!

Backing Selenium with WebDriver

Mon, 01 Jan 0001 00:00:00 +0000

(Previously located: https://github.com/SeleniumHQ/selenium/wiki/Selenium-Emulation)

Backing Selenium with WebDriver

The Java and .NET versions of WebDriver provide implementations of the existing Selenium API. In Java, it is used like so:

// You may use any WebDriver implementation. Firefox is used here as an example
WebDriver driver = new FirefoxDriver();

// A "base url", used by selenium to resolve relative URLs
String baseUrl = "http://www.google.com";

// Create the Selenium implementation
Selenium selenium = new WebDriverBackedSelenium(driver, baseUrl);

// Perform actions with selenium
selenium.open("http://www.google.com");
selenium.type("name=q", "cheese");
selenium.click("name=btnG");

// And get the underlying WebDriver implementation back. This will refer to the
// same WebDriver instance as the "driver" variable above.
WebDriver driverInstance = ((WebDriverBackedSelenium) selenium).getUnderlyingWebDriver();

Pros

Allows for WebDriver and Selenium to live side-by-side.
Provides a simple mechanism for a managed migration from the existing Selenium API to WebDriver’s.
Does not require the standalone Selenium RC server to be run

Cons

Does not implement every method
- But we’d love feedback!
Does also emulate Selenium Core
- So more advanced Selenium usage (that is, using “browserbot” or other built-in Javascript methods from Selenium Core) may need work
Some methods may be slower due to underlying implementation differences
Does not support Selenium’s “user extensions” (i.e., user-extensions.js)

Notes

After creating a WebDriverBackedSelenium instance with a given Driver, one does not have to call start() - as the creation of the Driver already started the session. At the end of the test, stop() should be called instead of the Driver’s quit() method.

Grid endpoints

Mon, 01 Jan 0001 00:00:00 +0000

Grid

Grid Status

Grid status provides the current state of the Grid. It consists of details about every registered Node. For every Node, the status includes information regarding Node availability, sessions, and slots.

curl --request GET 'http://localhost:4444/status'

Delete session

Deleting the session terminates the WebDriver session, quits the driver and removes it from the active sessions map. Any request using the removed session-id or reusing the driver instance will throw an error.

HTTP Client Configuration

Mon, 01 Jan 0001 00:00:00 +0000

These allow you to set various parameters for the HTTP library

package dev.selenium.drivers;

import dev.selenium.BaseTest;

import org.openqa.selenium.remote.http.ClientConfig;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import org.openqa.selenium.chrome.ChromeOptions;
import org.openqa.selenium.remote.RemoteWebDriver;

import javax.net.ssl.SSLContext;
import javax.net.ssl.TrustManager;
import javax.net.ssl.TrustManagerFactory;
import javax.net.ssl.X509TrustManager;
import java.io.FileInputStream;
import java.net.URL;
import java.nio.file.Path;
import java.security.KeyStore;
import java.security.cert.CertificateFactory;
import java.security.cert.X509Certificate;
import java.time.Duration;

import org.openqa.selenium.UsernameAndPassword;

import static java.net.http.HttpClient.Version.HTTP_1_1;

public class HttpClientTest extends BaseTest {
 URL gridUrl;

 @BeforeEach
 public void startGrid() {
 gridUrl = startStandaloneGridAdvanced();
 }

 @Test
 public void remoteWebDriverWithClientConfig() throws Exception {
 ClientConfig clientConfig = ClientConfig.defaultConfig()
 .withRetries()
 .sslContext(createSSLContextWithCA(Path.of("src/test/resources/tls.crt").toAbsolutePath().toString()))
 .connectionTimeout(Duration.ofSeconds(300))
 .readTimeout(Duration.ofSeconds(3600))
 .authenticateAs(new UsernameAndPassword("admin", "myStrongPassword"))
 .version(HTTP_1_1.toString());
 ChromeOptions options = getDefaultChromeOptions();
 options.setEnableDownloads(true);
 driver = RemoteWebDriver.builder()
 .oneOf(options)
 .address(gridUrl)
 .config(clientConfig)
 .build();
 }

 @Test
 public void remoteWebDriverIgnoreSSL() throws Exception {
 ClientConfig clientConfig = ClientConfig.defaultConfig()
 .withRetries()
 .sslContext(createIgnoreSSLContext())
 .connectionTimeout(Duration.ofSeconds(300))
 .readTimeout(Duration.ofSeconds(3600))
 .authenticateAs(new UsernameAndPassword("admin", "myStrongPassword"))
 .version(HTTP_1_1.toString());
 ChromeOptions options = getDefaultChromeOptions();
 options.setEnableDownloads(true);
 driver = RemoteWebDriver.builder()
 .oneOf(options)
 .address(gridUrl)
 .config(clientConfig)
 .build();
 }

 @Test
 public void remoteWebDriverWithEmbedAuthUrl() throws Exception {
 ClientConfig clientConfig = ClientConfig.defaultConfig()
 .withRetries()
 .sslContext(createSSLContextWithCA(Path.of("src/test/resources/tls.crt").toAbsolutePath().toString()))
 .connectionTimeout(Duration.ofSeconds(300))
 .readTimeout(Duration.ofSeconds(3600))
 .version(HTTP_1_1.toString());
 ChromeOptions options = getDefaultChromeOptions();
 options.setEnableDownloads(true);
 driver = RemoteWebDriver.builder()
 .oneOf(options)
 .address(embedAuthToUrl(gridUrl, "admin", "myStrongPassword"))
 .config(clientConfig)
 .build();
 }

 private URL embedAuthToUrl(URL url, String username, String password) throws Exception {
 String userInfo = username + ":" + password;
 String urlWithAuth = url.getProtocol() + "://" + userInfo + "@" + url.getHost() + ":" + url.getPort() + url.getPath();
 return new URL(urlWithAuth);
 }

 public static SSLContext createSSLContextWithCA(String caCertPath) throws Exception {
 FileInputStream fis = new FileInputStream(caCertPath);
 CertificateFactory cf = CertificateFactory.getInstance("X.509");
 X509Certificate caCert = (X509Certificate) cf.generateCertificate(fis);
 KeyStore keyStore = KeyStore.getInstance(KeyStore.getDefaultType());
 keyStore.load(null, null);
 keyStore.setCertificateEntry("caCert", caCert);
 TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
 tmf.init(keyStore);
 SSLContext sslContext = SSLContext.getInstance("TLS");
 sslContext.init(null, tmf.getTrustManagers(), null);
 return sslContext;
 }

 public static SSLContext createIgnoreSSLContext() throws Exception {
 TrustManager[] trustAllCerts = new TrustManager[]{
 new X509TrustManager() {
 public X509Certificate[] getAcceptedIssuers() {
 return null;
 }

 public void checkClientTrusted(X509Certificate[] certs, String authType) {
 }

 public void checkServerTrusted(X509Certificate[] certs, String authType) {
 }
 }
 };
 SSLContext sslContext = SSLContext.getInstance("TLS");
 sslContext.init(null, trustAllCerts, new java.security.SecureRandom());
 return sslContext;
 }
}

View on GitHub

import os
import pytest
import sys
from urllib3.util import Retry, Timeout
from selenium import webdriver
from selenium.webdriver.common.proxy import Proxy
from selenium.webdriver.common.proxy import ProxyType
from selenium.webdriver.remote.client_config import ClientConfig


@pytest.mark.skipif(sys.platform == "win32", reason="Gets stuck on Windows, passes locally")
def test_start_remote_with_client_config(grid_server):
 proxy = Proxy({"proxyType": ProxyType.AUTODETECT})
 retries = Retry(connect=2, read=2, redirect=2)
 timeout = Timeout(connect=300, read=3600)
 client_config = ClientConfig(remote_server_addr=grid_server,
 proxy=proxy,
 init_args_for_pool_manager={
 "init_args_for_pool_manager": {"retries": retries, "timeout": timeout}},
 ca_certs=_get_resource_path("tls.crt"),
 username="admin", password="myStrongPassword")
 options = get_default_chrome_options()
 driver = webdriver.Remote(command_executor=grid_server, options=options, client_config=client_config)
 driver.get("https://www.selenium.dev")
 driver.quit()


@pytest.mark.skipif(sys.platform == "win32", reason="Gets stuck on Windows, passes locally")
def test_start_remote_ignore_certs(grid_server):
 proxy = Proxy({"proxyType": ProxyType.AUTODETECT})
 client_config = ClientConfig(remote_server_addr=grid_server,
 proxy=proxy,
 timeout=3600,
 ignore_certificates=True,
 username="admin", password="myStrongPassword")
 options = get_default_chrome_options()
 driver = webdriver.Remote(command_executor=grid_server, options=options, client_config=client_config)
 driver.get("https://www.selenium.dev")
 driver.quit()


def _get_resource_path(file_name: str):
 if os.path.abspath("").endswith("tests"):
 path = os.path.abspath(f"resources/{file_name}")
 else:
 path = os.path.abspath(f"tests/resources/{file_name}")
 return path

def get_default_chrome_options():
 options = webdriver.ChromeOptions()
 options.add_argument("--no-sandbox")
 return options

View on GitHub

Add Example

HTTP response codes

Mon, 01 Jan 0001 00:00:00 +0000

For some browser configurations in Selenium RC, Selenium acted as a proxy between the browser and the site being automated. This meant that all browser traffic passed through Selenium could be captured or manipulated. The captureNetworkTraffic() method purported to capture all of the network traffic between the browser and the site being automated, including HTTP response codes.

Selenium WebDriver is a completely different approach to browser automation, preferring to act more like a user. This is represented in the way you write tests with WebDriver. In automated functional testing, checking the status code is not a particularly important detail of a test’s failure; the steps that preceded it are more important.

Page object models

Mon, 01 Jan 0001 00:00:00 +0000

Note: this page has merged contents from multiple sources, including the Selenium wiki

Overview

Within your web app’s UI, there are areas where your tests interact with. A Page Object only models these as objects within the test code. This reduces the amount of duplicated code and means that if the UI changes, the fix needs only to be applied in one place.

Page Object Model is a Design Pattern that has become popular in test automation for enhancing test maintenance and reducing code duplication. A page object is an object-oriented class that serves as an interface to a page of your AUT. The tests then use the methods of this page object class whenever they need to interact with the UI of that page. The benefit is that if the UI changes for the page, the tests themselves don’t need to change, only the code within the page object needs to change. Subsequently, all changes to support that new UI are located in one place.

Selenium Manager (Beta)

Mon, 01 Jan 0001 00:00:00 +0000

Motivation

TL;DR: Selenium Manager is the official driver manager of the Selenium project, and it is shipped out of the box with every Selenium release.

Selenium uses the native support implemented by each browser to carry out the automation process. For this reason, Selenium users need to place a component called driver (chromedriver, geckodriver, msedgedriver, etc.) between the script using the Selenium API and the browser. For many years, managing these drivers was a manual process for Selenium users. This way, they had to download the required driver for a browser (chromedriver for Chrome, geckodriver for Firefox, etc.) and place it in the PATH or export the driver path as a system property (Java, JavaScript, etc.). But this process was cumbersome and led to maintainability issues.

Driver Service Class

Mon, 01 Jan 0001 00:00:00 +0000

The Service classes are for managing the starting and stopping of local drivers. They cannot be used with a Remote WebDriver session.

Service classes allow you to specify information about the driver, like location and which port to use. They also let you specify what arguments get passed to the command line. Most of the useful arguments are related to logging.

Default Service instance

To start a driver with a default service instance:

TOML configuration options

Mon, 01 Jan 0001 00:00:00 +0000

All the options shown in CLI options can be configured through a TOML file. This page shows configuration examples for the different Grid components.

Overview

Selenium Grid uses TOML format for config files. The config file consists of sections and each section has options and its respective value(s).

Buck Build Tool

Mon, 01 Jan 0001 00:00:00 +0000

This documentation previously located on the wiki
You can read the documentation for the legacy Crazy Fun Build tool.

Building Selenium with Buck

The easiest thing to do is to just run “./go”. The build process will download the right version of Buck for you so long as there’s no .nobuckcheck file in the root of the project. The download ends up in buck-out/crazy-fun/HASH/buck.pex where HASH is the value of the current buck version (given in the .buckversion file in the root of the project.

Chrome specific functionality

Mon, 01 Jan 0001 00:00:00 +0000

By default, Selenium 4 is compatible with Chrome v75 and greater. Note that the version of the Chrome browser and the version of chromedriver must match the major version.

Options

Capabilities common to all browsers are described on the Options page.

Capabilities unique to Chrome and Chromium are documented at Google’s page for Capabilities & ChromeOptions

Starting a Chrome session with basic defined options looks like this:

 System.clearProperty(ChromeDriverService.CHROME_DRIVER_LOG_LEVEL_PROPERTY);
 }

View Complete Code View on GitHub

 options = get_default_chrome_options()
 driver = webdriver.Chrome(options=options)

View Complete Code View on GitHub

 {
 var options = new ChromeOptions();

View Complete Code View on GitHub

 options = Selenium::WebDriver::Options.chrome
 @driver = Selenium::WebDriver.for :chrome, options: options

View Complete Code View on GitHub

 const Options = new Chrome.Options();
 let driver = new Builder()
 .forBrowser(Browser.CHROME)
 .setChromeOptions(Options)
 .build();

View Complete Code View on GitHub

Add Example

Working with cookies

Mon, 01 Jan 0001 00:00:00 +0000

A cookie is a small piece of data that is sent from a website and stored in your computer. Cookies are mostly used to recognise the user and load the stored information.

WebDriver API provides a way to interact with cookies with built-in methods:

It is used to add a cookie to the current browsing context. Add Cookie only accepts a set of defined serializable JSON object. Here is the link to the list of accepted JSON key values

Customizing a Node

Mon, 01 Jan 0001 00:00:00 +0000

How to customize a Node

There are times when we would like a Node to be customized to our needs.

For e.g., we may like to do some additional setup before a session begins execution and some clean-up after a session runs to completion.

Following steps can be followed for this:

Create a class that extends org.openqa.selenium.grid.node.Node
Add a static method (this will be our factory method) to the newly created class whose signature looks like this:

Domain specific language

Mon, 01 Jan 0001 00:00:00 +0000

A domain specific language (DSL) is a system which provides the user with an expressive means of solving a problem. It allows a user to interact with the system on their terms – not just programmer-speak.

Your users, in general, do not care how your site looks. They do not care about the decoration, animations, or graphics. They want to use your system to push their new employees through the process with minimal difficulty; they want to book travel to Alaska; they want to configure and buy unicorns at a discount. Your job as tester is to come as close as you can to “capturing” this mind-set. With that in mind, we set about “modeling” the application you are working on, such that the test scripts (the user’s only pre-release proxy) “speak” for, and represent the user.

Unable to Locate Driver Error

Mon, 01 Jan 0001 00:00:00 +0000

Historically, this is the most common error beginning Selenium users get when trying to run code for the first time:

The path to the driver executable must be set by the webdriver.chrome.driver system property; for more information, see https://chromedriver.chromium.org/. The latest version can be downloaded from https://chromedriver.chromium.org/downloads

The executable chromedriver needs to be available in the path.

The file geckodriver does not exist. The driver can be downloaded at https://github.com/mozilla/geckodriver/releases"

Unable to locate the chromedriver executable;

Likely cause

Through WebDriver, Selenium supports all major browsers. In order to drive the requested browser, Selenium needs to send commands to it via an executable driver. This error means the necessary driver could not be found by any of the means Selenium attempts to use.

Adding new drivers to Selenium 2 code

Mon, 01 Jan 0001 00:00:00 +0000

This documentation previously located on the wiki \

Introduction

WebDriver has a comprehensive suite of tests that describe the expected behavior of a new implementation. We’ll assume that you’re implementing the driver in Java for the sake of simplicity, but you can take a look at any of the existing implementations for how we handle more complex builds or other languages once you’ve read this.

Writing a New WebDriver Implementation

Create New Top-Level Directories

Create a new top-level folder, parallel to “common” and “firefox”, named after your browser. In this, create a “src/java” and a “test/java” directory. It should be obvious what goes where.

Legacy Firefox Driver

Mon, 01 Jan 0001 00:00:00 +0000

This documentation previously located on the wiki
You can read more about geckodriver.

About

Firefox driver is included in the selenium-server-stanalone.jar available in the downloads. The driver comes in the form of an xpi (firefox extension) which is added to the firefox profile when you start a new instance of FirefoxDriver.

Pros

Runs in a real browser and supports Javascript
Faster than the InternetExplorerDriver

Cons

Slower than the HtmlUnitDriver

Important System Properties

The following system properties (read using System.getProperty() and set using System.setProperty() in Java code or the “-DpropertyName=value” command line flag) are used by the FirefoxDriver:

Gmail, email and Facebook logins

Mon, 01 Jan 0001 00:00:00 +0000

For multiple reasons, logging into sites like Gmail and Facebook using WebDriver is not recommended. Aside from being against the usage terms for these sites (where you risk having the account shut down), it is slow and unreliable.

The ideal practice is to use the APIs that email providers offer, or in the case of Facebook the developer tools service which exposes an API for creating test accounts, friends and so forth. Although using an API might seem like a bit of extra hard work, you will be paid back in speed, reliability, and stability. The API is also unlikely to change, whereas webpages and HTML locators change often and require you to update your test framework.

Setting up your own Grid 3

Mon, 01 Jan 0001 00:00:00 +0000

To use Selenium Grid, you need to maintain your own infrastructure for the nodes. As this can be a cumbersome and time intense effort, many organizations use IaaS providers such as Amazon EC2 and Google Compute to provide this infrastructure.

Other options include using providers such as Sauce Labs or Testing Bot who provide a Selenium Grid as a service in the cloud. It is certainly possible to also run nodes on your own hardware. This chapter will go into detail about the option of running your own grid, complete with its own node infrastructure.

Information about web elements

Mon, 01 Jan 0001 00:00:00 +0000

There are a number of details you can query about a specific element.

Is Displayed

This method is used to check if the connected Element is displayed on a webpage. Returns a Boolean value, True if the connected element is displayed in the current browsing context else returns false.

This functionality is mentioned in, but not defined by the w3c specification due to the impossibility of covering all potential conditions. As such, Selenium cannot expect drivers to implement this functionality directly, and now relies on executing a large JavaScript function directly. This function makes many approximations about an element’s nature and relationship in the tree to return a value.

Logging Selenium commands

Mon, 01 Jan 0001 00:00:00 +0000

Turning on logging is a valuable way to get extra information that might help you determine why you might be having a problem.

Getting a logger

Java logs are typically created per class. You can work with the default logger to work with all loggers. To filter out specific classes, see Filtering

Mouse actions

Mon, 01 Jan 0001 00:00:00 +0000

There are only 3 actions that can be accomplished with a mouse: pressing down on a button, releasing a pressed button, and moving the mouse. Selenium provides convenience methods that combine these actions in the most common ways.

Click and hold

This method combines moving the mouse to the center of an element with pressing the left mouse button. This is useful for focusing a specific element:

 WebElement clickable = driver.findElement(By.id("clickable"));
 new Actions(driver)
 .clickAndHold(clickable)
 .perform();

View Complete Code View on GitHub

 clickable = driver.find_element(By.ID, "clickable")
 ActionChains(driver) \
 .click_and_hold(clickable) \
 .perform()

View Complete Code View on GitHub

 IWebElement clickable = driver.FindElement(By.Id("clickable"));
 new Actions(driver)
 .ClickAndHold(clickable)
 .Perform();

View Complete Code View on GitHub

 clickable = driver.find_element(id: 'clickable')
 driver.action
 .click_and_hold(clickable)
 .perform

View Complete Code View on GitHub

 let clickable = driver.findElement(By.id("clickable"));
 const actions = driver.actions({async: true});
 await actions.move({origin: clickable}).press().perform();

View Complete Code View on GitHub

 .clickAndHold(clickable)
 .perform()

 Assertions.assertEquals("focused", driver.findElement(By.id("click-status")).getText())

View Complete Code View on GitHub

Click and release

This method combines moving to the center of an element with pressing and releasing the left mouse button. This is otherwise known as “clicking”:

Chrome DevTools Network Features

Mon, 01 Jan 0001 00:00:00 +0000

While Selenium 4 provides direct access to the Chrome DevTools Protocol, these methods will eventually be removed when WebDriver BiDi implemented.

Basic authentication

Some applications make use of browser authentication to secure pages. It used to be common to handle them in the URL, but browsers stopped supporting this. With this code you can insert the credentials into the header when necessary

 Predicate<URI> uriPredicate = uri -> uri.toString().contains("herokuapp.com");
 Supplier<Credentials> authentication = UsernameAndPassword.of("admin", "admin");
 ((HasAuthentication) driver).register(uriPredicate, authentication);

View Complete Code View on GitHub

 credentials = base64.b64encode("admin:admin".encode()).decode()
 auth = {'authorization': 'Basic ' + credentials}
 await connection.session.execute(connection.devtools.network.set_extra_http_headers(Headers(auth)))

View Complete Code View on GitHub

 var handler = new NetworkAuthenticationHandler()
 {
 UriMatcher = uri => uri.AbsoluteUri.Contains("herokuapp"),
 Credentials = new PasswordCredentials("admin", "admin")
 };
 var networkInterceptor = driver.Manage().Network;
 networkInterceptor.AddAuthenticationHandler(handler);
 await networkInterceptor.StartMonitoring();

View Complete Code View on GitHub

 driver.register(username: 'admin',
 password: 'admin',
 uri: /herokuapp/)

View Complete Code View on GitHub

Implementation Missing

Legacy Selenium IDE Release Notes

Mon, 01 Jan 0001 00:00:00 +0000

This documentation previously located on the wiki

2.9.1 - to be released

Fix - Fixes https://github.com/SeleniumHQ/selenium/issues/396
Fix - Changed Google code links to GitHub.
Enh - Merged official language plugins into the main xpi eliminating the need for multi-xpi with the main xpi and multiple language plugin xpis.
Fix - Fixes https://github.com/SeleniumHQ/selenium/issues/570

2.9.0

Enh - Schedule tests for automatic playback at a certain time or periodic intervals. (http://blog.reallysimplethoughts.com/2015/03/09/selenium-ide-scheduler-has-arrived-part-1/)
Enh - Allow submission of diagnostic information via a gist.
Enh - Improved health logging, including alerts normally hidden.

2.8.0

New - Added visual assist option to help users requiring stronger constrast in colors, turned off by default. Turn it on from the Options dialog. - Issue 7696 (on Google Code)
New - Health Service to catch unhandled exceptions, statistics, metrics and diagnostics
Enh - Added Search Issues menu item in Help menu to make it easier to search all issues so that we do not get so many duplicate reports of the same issue
Fix - Fixed broken autocomplete - issue 7928 (on Google Code)
Fix - Fixed cancelling of select button when page is reloaded - issue 7793 (on Google Code)
Fix - Adding select button to the sidebar and reduced button size - issue 7815 (on Google Code)

2.7.0

Fix - Fixed switching between tabs in the bottom info panel in FF32 - issue 7824 (on Google Code)
Fix - Fixes for https://bugzilla.mozilla.org/show_bug.cgi?id=1016305
Enh - Let comments (and commands) span the full width of the commands table
Enh - Show the result of the test case in the log after it has been played
Enh - Group items in the Action menu by function
Enh - Collect more statistics about test case and suite including running time for reporting purposes
Enh - Improved listboxes supporting drag and drop reordering
Enh - Provide common utility function for plugin authors to deal with files
Enh - Allow pressing tab in the command text box to accept the current autocomplete and move to the target text box
Enh - Select an autocomplete match when typing in the command text box to speed up manual entry of commands
Enh - Make promises implementation available via deferred.js for plugin developers
Enh - Make simple http functions available for plugin developers
Enh - Easier to use confirmations for internal use and for plugins
Fix - Disable autocomplete when editing comments
Fix - Fixed error TypeError: command.isRollup is not a function
Fix - Fixed TypeError: debugContext.currentCommand is undefined
Fix - Fixed TypeError: this.treebox is undefined treeView.js
Fix - Various errors when selecting a comment (usually hidden from the user)
Fix - Incorrect doctype in overlay
Fix - Adding Selenium IDE item under Settings->Developer menu - issue 7268 (on Google Code)
Fix - Ignore Firefox developer tools while recording

2.6.0

Fix - Fixed broken autocompletion in FF31+ - issue 7645 (on Google Code)
Fix - Fixed options validation on options reset - issue 1050 (on Google Code)
Fix - Fixed C# code formatting for select elements

2.5.0

Enh - Select an element for a command by clicking on the element in the browser window (http://blog.reallysimplethoughts.com/2014/01/05/manually-adding-and-updating-element-locators-the-easy-way/)
Enh - Start playing a test suite from any test case (Using right click menu) - issue 1987 (on Google Code)
Enh - Add a new test case using a keyboard shortcut (ctrl-N or cmd+N)
Fix - Fixed delete test case through right click menu was sometimes disabled - issue 5003 (on Google Code)
Fix - Fixed Selenium IDE icon is sometimes not visible - issue 5712 (on Google Code)
Fix - Fixed selectWindow using a variable - issue 3270 (on Google Code)
Some minor changes

2.4.0

Enh - Base URL history, recent test cases and recent test suites can be cleared - issue 6135 (on Google Code)
Enh - Special key now have shorter names (http://blog.reallysimplethoughts.com/2013/09/25/using-special-keys-in-selenium-ide-part-2/)
Enh - Support for user extensions in Webdriver playback - issue 5675 (on Google Code)
Fix - The recording of entering text in fields uses type instead of sendKeys.
Enh - When developer tools are active, the last open test case or suite is automatically opened
Fix - Fixed is* commands in Webdriver playback in Selenium IDE - issue 6118 (on Google Code)
Enh - Adding ability to show commands as deprecated in Selenium IDE and smartness to show the correct alternative command
Enh - Deprecating Selenium IDE commands *TextPresent, typeKeys, keyUp, keyDown and keyPress
Enh - Import json library in exported Ruby Webdriver tests
Enh - Adding support for waitFor* and waitForNot* commands in Webdriver playback - issue 5913 (on Google Code)

2.3.0

New - Added support for HTML5 input fields recording - issue 3765 (on Google Code)
New - Recording for sendKeys command
Enh - Removal of deprecated *TextPresent commands from right click menu
Fix - Dead object error in recording IDE tests - issue 4761 (on Google Code)
Fix - Fixed could not continue in recording - issue 5820 (on Google Code)
Enh - UTF-8 encoded user-extensions.js support - issue 1646 (on Google Code)
New special keys support for sendKeys in Selenium IDE and webdriver playback - issue #6052 (on Google Code)
New - Special keys support to sendKeys in all official formatters - issue 6053 (on Google Code) (http://blog.reallysimplethoughts.com/2013/09/25/using-special-keys-in-selenium-ide-part-1/)
Enh - Plugin api enhancement for specifying formatter type + documentaton comments
Fix - Invalid XPath error in Firefox 23 - issue 6055 (on Google Code)
New - Added support for Firefox 23

2.2.0

Fix - keyUp, keyDown, keyPress, typeKeys fixed on Firefox 22 - issue 5883 (on Google Code), issue 5884 (on Google Code)

2.1.0

Enh - Plugin system changed (http://blog.reallysimplethoughts.com/2013/07/07/changes-to-selenium-ide-plugin-system/)
New - Added support for Firefox 22 + 23 beta
Fix - Click fixed for Firefox 22 - issue 5841 (on Google Code)

2.0.0

New - WebDriver playback support (http://blog.reallysimplethoughts.com/2013/02/18/webdriver-playback-in-selenium-ide-is-here/)
New - Added support for Firefox 19 & 20
New - Selenium IDE icon on toolbar is added on first install

1.10.0

New - Added support for Firefox 16 & 17
New - Implemented formatting for alert handling commands
Bug - Fixed options for Java 4 WebDriver formatter
Bug - Processing locators before use in getCssCount and getXpathCount. Fixes issue 4784 (on Google Code)

1.9.1

New - Added support for Firefox 15
New - Added support for assertTextPresent, verifyTextPresent, waitForTextPresent, assertTextNotPresent, verifyTextNotPresent, waitForTextNotPresent commands to WebDriver formatters. (http://blog.reallysimplethoughts.com/2012/08/26/selenium-ide-webdriver-formatters-updated-to-support-textpresent-commands/)
New - Added the target and value parameters in comments when the WebDriver formatters do not support the command

1.9.0

New - Added Selenese command sendKeys (http://blog.reallysimplethoughts.com/2012/07/19/new-selenese-command-sendkeys/)
New - Better naming of formatters
New - Added support for Firefox 14

1.8.1

New - Added support for Firefox 13

1.8.0

New - Added support for Firefox 12

1.7.2

Bug - Fixed regression with typing into file input fields - issue 3549 (on Google Code)

1.7.1

Bug - Fixed regression with stored variables - issue 3520 (on Google Code)

1.7.0

New - Added additional useful menu items to the help menu
New - Added support for Firefox 11
Bug - Stored variables can safely contain consecutive dollar signs - issue 834 (on Google Code)
Bug - Don’t trim whitespace when decoding HTML testcases - issue 755 (on Google Code)
New - Formatter menu items are now context sensitive - issue 3327 (on Google Code) and issue 3385 (on Google Code)
Bug - Fixed Ruby WebDriver test suite export - issue 3243 (on Google Code)
Bug - File extensions being added to all file pickers - issue 3336 (on Google Code)
Bug - Record interactions with elements with an id of ‘id’ - issue 3273 (on Google Code)

1.6.0

New - Added support for Firefox 10
New - Added keyboard shortcuts to launch Selenium IDE - issue 3028 (on Google Code)
Bug - Added break command to autocomplete list - issue 3046 (on Google Code)
Bug - Incorrect tooltip displayed in sidebar - issue 3098 (on Google Code)
Bug - Improved XPath locator recording when there are multiple matches - issue 3056 (on Google Code)
Bug - Locators can now be reordered on Mac - issue 3267 (on Google Code)

1.5.0

New - Added support for Firefox 9
Bug - Changes to user extensions weren’t being updated in Firefox 8 - issue 2801 (on Google Code)
Bug - Security error was thrown when trying to type into file (upload) input fields in Firefox 8 - issue 2826 (on Google Code)
Bug - Improved French locale - issue 1912 (on Google Code)
Bug - break command was failing - issue 725 (on Google Code)
Bug - source view is now fixed width (monospace) - issue 522 (on Google Code)
New - Implemented ‘select’ formatting for WebDriver bindings (Java, C#, Python, Ruby)
Bug - Fixed compile-time and run-time errors in the code formatted for WebDriverBackedSelenium
Bug - Fixed ‘baseUrl’ and ‘get’ formatting errors in various formatters to handle relative and absolute URLs

1.4.1

Bug - Apparently I shipped without switching all the version numbers correctly. (Adam)

1.4.0

New - Firefox 8 support (again, just a version max version bump)

1.3.0

Was going to be just a quick release to get

When to Use Grid

Mon, 01 Jan 0001 00:00:00 +0000

When would you use a Selenium Grid?

To run your tests in parallel, against different browser types, browser versions, operating systems
To reduce the time needed to execute a test suite

Selenium Grid runs test suites in parallel against multiple machines (called Nodes). For large and long-running test suites, this can save minutes, hours, or perhaps days. This shortens the turnaround time for test results as your application under test (AUT) changes.

Edge specific functionality

Mon, 01 Jan 0001 00:00:00 +0000

Microsoft Edge is implemented with Chromium, with the earliest supported version of v79. Similar to Chrome, the major version number of edgedriver must match the major version of the Edge browser.

Options

Capabilities common to all browsers are described on the Options page.

Capabilities unique to Chromium are documented at Google’s page for Capabilities & ChromeOptions

Starting an Edge session with basic defined options looks like this:


 @Test

View Complete Code View on GitHub

 options = get_default_edge_options()

View Complete Code View on GitHub

 {
 var options = new EdgeOptions();

View Complete Code View on GitHub

 options = Selenium::WebDriver::Options.edge
 @driver = Selenium::WebDriver.for :edge, options: options

View Complete Code View on GitHub

 let options = new edge.Options();
 driver = new Builder()
 .forBrowser(Browser.EDGE)
 .setEdgeOptions(options)
 .build();

View Complete Code View on GitHub

Add Example

Selenium

Browsing Context

Commands

Open a new window

/examples/java/src/test/java/dev/selenium/bidirectional/webdriver_bidi/BrowsingContextTest.java

Captchas

Selenium components

Terminology

The Parts and Pieces

Copyright and attributions

The Documentation of Selenium

Design patterns and development strategies

Overview

Waiting with Expected Conditions

Configuration help

Info Command

Config help

Input

Perform Actions

/examples/java/src/test/java/dev/selenium/bidirectional/webdriver_bidi/ActionsTest.java

Locator strategies

Traditional Locators

Creating Locators

Log

Console logs

/examples/java/src/test/java/dev/selenium/bidirectional/webdriver_bidi/LogTest.java

WebDriver BiDi Logging Features

Console Message Handlers

Add Handler

Browser navigation

Navigate to

/examples/java/src/test/java/dev/selenium/interactions/NavigationTest.java

/examples/python/tests/interactions/test_navigation.py

/examples/dotnet/SeleniumDocs/Interactions/NavigationTest.cs

/examples/ruby/spec/interactions/navigation_spec.rb

/examples/javascript/test/interactions/navigation.spec.js

Back

WebDriver BiDi Network Features

Authentication Handlers

Network

Commands

Add network intercept

/examples/java/src/test/java/dev/selenium/bidirectional/webdriver_bidi/NetworkCommandsTest.java

Observability in Selenium Grid

Table of Contents

Selenium Grid

Observability

Distributed tracing

Overview of Test Automation

WebDriver BiDi Script Features

Script Pinning

Execute Script

DOM Mutation Handlers

Script

Commands

Call function in a browsing context

/examples/java/src/test/java/dev/selenium/bidirectional/webdriver_bidi/ScriptTest.java

JavaScript alerts, prompts and confirmations

Alerts

CLI options in the Selenium Grid

Contributing to the Selenium site & documentation

Crazy Fun Build Tool

Targets

A deeper look at Selenium

Selenium controls web browsers

File downloads

Finding web elements

First matching element

Getting started with Selenium Grid

Quick start

GraphQL query support

Enums

Grid 3

HTML runner

Common information

Example Linux environment

Install a Selenium library

Requirements by language

Interacting with web elements

Additional validations