Learn how to design a test automation framework for automating web-based applications.

Test Automation

Testing the user interface for any application is generally time-consuming when done for each new release. UI test automation is the most common and effective way to simulate the actual user journey and business use cases for any application.

In this module, we’ll learn to design a test automation framework from scratch to automate any web-based application using Java, Selenium, and TestNG. We’ll start by learning the basics of Selenium and TestNG and then learn about build management, logging, and reporting, all of which are key concepts for any QA engineer or developer. By the end of this module, we will successfully create a UI test automation framework.

Design a Test Automation Framework with Selenium and Java

Selenium has its own set of exceptions while writing automation scripts. A programmer has to handle or throw those exceptions. 

# WebDriver exception

All runtime exception classes in Selenium WebDriver come under the superclass `WebDriverException`. 

The most common exceptions under WebDriverException class are:

* `NoSuchElementException` -  the element is not found during runtime using `FindBy` method
* `StaleElementReferenceException` -  the referenced element is no longer present on the DOM page
* `NoSuchWindowException` - switching to an invalid window
* `InvalidSelectorException` - wrong or invalid selector used to find an element
* `ElementNotSelectableException` - the element present but disabled in the DOM
* `TimeoutException` - the element didn’t display in the specified time
* `NoSuchFrameException` - switching to an invalid frame
* `NoAlertPresentException` - switching to an invalid alert
* `ElementNotVisibleException` - when an element is present in the DOM but cannot be interacted with, e.g., Hidden Elements

In this lesson, we’ll learn about the set of exceptions provided by the Selenium.

Exception Handling