WebDriver Introduction
Selenium WebDriver Architecture
Introduction to WebDriver API
Introduction to WebDriver – Code
Handling Dropdowns and Select class
Handling Multiple Dropdown values and Links
Handling Radio buttons and Checkboxes
Capture Screenshots and Email test results
Browser Navigation Methods
Handling tabs
Capturing screenshot, Handling tabs and pop-ups – Code
Handling tabs and Pop-ups – Code
Handling Alerts
Handling User Authentication and Input alerts
HtmlUnitDriver and Handling Captchas
Handling Web Tables
Synchronization
Handling WebTables, Synchronization issues, Firefoxprofiles – Code
Actions Class
Event Listeners, Event Firing Mouse, Coordinates – Code
Handling Mouse Hover in Selenium
JavascriptExecutor
Handling Iframes
IsElementPresent, IsEnabled, IsSelected
Working with Chrome Driver - Part 1
Working with FireFox Driver - Part 2
Working with Internet Explorer Driver - Part 3
Handling SSL Certificate
Desired Capabilities
How to Encode password in WebDriver
Handling JQuery Elements - Drag and Drop, Sliders, Resizable
Handling JQuery Elements - Drag and Drop, Sliders, Resizable – Code
Working on IE Browser using Actions
TestNG, Ant & Report Generation through XSLT
Introduction to TestNG and Annotations
TestNG Parameterization
Configuring ANT, Generating TestNG & XSLT Reports
Code for generating XSLT / Surefire Reports through MAVEN
TestNG Parameterization Excel Reading
Handling Multiple data providers
TestNG XSLT Jar, Build.xml & TestNG.xml file
Frameworks Introduction
Hybrid (DATA + KEYWORD) driven Framework
Framework Architecture
Reading Excel sheets
TestNG DataProvider
Data Provider with Hashtable
Handling Multiple Test Suites
Multiple DataProviders
Setting up Run-modes at Suite Level
Setting up Runmodes at TestCase Level
Creating a common utility for Run-modes
Hybrid Framework Code
WebDriver operational architecture shows how exactly WebDriver forms the communication channel among test code, browser driver, and the browsers. These three communicates with each other over some medium as:
Test code communicates to browser driver using JSON Wire protocol, and the Browser driver creates communication with the browser over HTTP.
Language Bindings & JSON Wire Protocol:
As we are aware that Selenium provides support to a set of programming languages such as Java, Ruby, Python, C#, JavaScript, and Kotlin. These language bindings are the primary source of the interaction of users, which connects to browser drivers through JSON wire protocol.
JSON Wire protocol is a way to represent the user requests which are sent to browser driver using WebDriver API.
Browser drivers and Browser interactions:
Once the browser driver gets the commands given by tester in the form of the API calls, the driver interacts with the browser, and the browser executes these commands to fulfil the expectations of the tester. This is a two-way process between the browser driver and browser. The communication which takes place between this driver and browser happens over an HTTP server.
WebDriver removes the need to have a launch of the Selenium RC server, and hence this was the main reason for merging the Selenium RC project with the WebDriver project.
Don't miss out!
Study Material
Quiz