Overview of Selenium Architecture

Selenium Web Driver API Architecture:

Webdriver doesn't help us running the Test cases nor doesn't it help us in reports generation/batch running/ordering the test case execution/excel file reading but it just helps us to interact with the browser using the webdriver commands

“WebDriver”: Is an interface comes under this package of Selenium and a sub interface of “SearchContext”. “SearchContext” consists of “WebDriver” & “WebElement” as a sub interfaces.

What is “GeckoDriver”:

It is a WebDriver which is used to interact with WebApps. So, this means that all the drivers should have all the implementations which are contracted in the WebDriver interfaces and all the Drivers can be called as WebDriver.

Web Page composed of Web Elements and these Drivers’s will communicate with the Web Page. For communicating with Web Page means communication with Elements present on the Web Page like for example: “Textboxes”, Buttons”, “Links” etc. “WebElement” a sub interface of “SearchContext” comes into picture.

Webdriver doesn't help us running the Test cases nor doesn't it help us in reports generation/batch running/ordering the test case execution/excel file reading but it just helps us to interact with the browser using the webdriver commands