RemoteWebDriver is an implementation class of the WebDriver interface that a test-script developer can use to execute their test scripts via the Selenium Standalone server on a remote machine. There are two parts to RemoteWebDriver: a server and a client. Before we start working with them, let's rewind and see what we've been doing.

The following diagram explains what we've done so far:

The test script using WebDriver client libraries, Chrome Driver (or IE Driver or Gecko Driver for Firefox), and Chrome browser (or IE browser or Firefox browser) is sitting on the same machine. The browser is loading the web application, which may or may not be hosted remotely; anyway, this is outside the scope of our discussion. We will discuss different scenarios of test-script execution, as follows:

The test script is located on a local machine, while the browsers are installed on a remote machine. In this scenario, RemoteWebDriver comes into the picture. As mentioned earlier, there are two components associated with RemoteWebDriver: the server and the client. Let's start with the Selenium Standalone server.