RemoteWebDriveris an implementation class of the
WebDriverinterface that a test script developer can use to execute their test scripts via the
RemoteWebDriverserver on a remote machine.
- There are two parts to
RemoteWebDriver: a server and a client
RemoteWebDriverserver is a component that listens on a port for various requests from a
RemoteWebDriverclient. Once it receives the requests, it forwards them to any of the following: Firefox Driver, IE Driver, or Chrome Driver, whichever is asked.
- The language-binding client libraries that serve as a
RemoteWebDriverclient. The client, as it used to when executing tests locally, translates your test script requests to JSON payload and sends them across to the
RemoteWebDriverserver using the JSON wire protocol.
- When you execute your tests locally, the WebDriver client libraries talk to your Firefox Driver, IE Driver, or Chrome Driver directly. Now, when you try to execute your tests remotely, the WebDriver client libraries talk to the
RemoteWebDriverserver and the server talks to either the Firefox Driver, IE Driver, or Chrome Driver, whichever the WebDriver client asks for.