Delve into designing a test automation framework using Java and Selenium. Learn about Selenium basics, TestNG, build management, logging, and reporting to automate web applications effectively.

ui-test.tar.gz

Java

TestNG

Bash

ui-test

ui-test-1

ui-test-frmk

ui-frmk

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 course, you will learn how to design a test automation framework from scratch for automating any web-based application using Java, Selenium, and TestNG. You’ll start by learning the basics of Selenium and TestNG and then move on to learn about build management, logging, and reporting, which are key learnings for any QA engineer or developer. By the end of this course, you will have successfully created a UI test automation framework.

Design a Test Automation Framework with Selenium and Java

# Logback

[Logback](http://logback.qos.ch/) is intended as a successor to the popular log4j project that is used for logging to console and file. The main advantage of using *logback* over *log4j* is that its internals has been re-written to perform about ten times faster and has a smaller memory footprint as well. 


[Here](http://logback.qos.ch/reasonsToSwitch.html), we can find a reason to use logback over log4j.

# Dependency to add

## Maven

```xml
<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>1.2.3</version>
</dependency>

```

## Gradle

```

compile group: 'ch.qos.logback', name: 'logback-classic', version: '1.2.3'

```

A sample ***logback.xml*** for logging to console and writing to file:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<configuration>

	<appender name="CONSOLE"
		class="ch.qos.logback.core.ConsoleAppender">
		<append>false</append>
		<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
			<level>info</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
		<immediateFlush>false</immediateFlush>
	</appender>
	<appender name="WARN" class="ch.qos.logback.core.FileAppender">
		<file>logs/warn.log</file>
		<append>false</append>
		<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
			<level>warn</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>
	<appender name="DEBUG"
		class="ch.qos.logback.core.FileAppender">
		<file>logs/debug.log</file>
		<append>false</append>
		<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
			<level>debug</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>
	<appender name="INFO" class="ch.qos.logback.core.FileAppender">
		<file>logs/info.log</file>
		<append>false</append>
		<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
			<level>info</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>
	<appender name="ERROR"
		class="ch.qos.logback.core.FileAppender">
		<file>logs/error.log</file>
		<append>false</append>
		<filter class="ch.qos.logback.classic.filter.ThresholdFilter">
			<level>error</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>

	<root level="DEBUG">
		<appender-ref ref="CONSOLE" />
		<appender-ref ref="INFO" />
		<appender-ref ref="DEBUG" />
		<appender-ref ref="WARN" />
		<appender-ref ref="ERROR" />
	</root>

</configuration>
```

# Logback

[Logback](http://logback.qos.ch/) is intended as a successor to the popular log4j project that is used for logging to console and file. The main advantage of using *logback* over *log4j* is that its internals has been re-written to perform about ten times faster and has a smaller memory footprint as well. 


[Here](http://logback.qos.ch/reasonsToSwitch.html), we can find a reason to use logback over log4j.

# Dependency to add

## Maven

```xml
<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>1.2.3</version>
</dependency>

```

## Gradle

```

compile group: 'ch.qos.logback', name: 'logback-classic', version: '1.2.3'

```

A sample ***logback.xml*** for logging to console and writing to file:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<configuration>

	<appender name="CONSOLE"
	>
		<append>false</append>
		<filter>
			<level>info</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
		<immediateFlush>false</immediateFlush>
	</appender>
	<appender name="WARN">
		<file>logs/warn.log</file>
		<append>false</append>
		<filter>
			<level>warn</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>
	<appender name="DEBUG"
	>
		<file>logs/debug.log</file>
		<append>false</append>
		<filter>
			<level>debug</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>
	<appender name="INFO">
		<file>logs/info.log</file>
		<append>false</append>
		<filter>
			<level>info</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>
	<appender name="ERROR"
	>
		<file>logs/error.log</file>
		<append>false</append>
		<filter>
			<level>error</level>
		</filter>
		<encoder>
			<pattern>%d{HH:mm:ss.SSS} %-5level %logger{36} - %msg - \(%file:%line\) %n</pattern>
		</encoder>
	</appender>

	<root level="DEBUG">
		<appender-ref ref="CONSOLE" />
		<appender-ref ref="INFO" />
		<appender-ref ref="DEBUG" />
		<appender-ref ref="WARN" />
		<appender-ref ref="ERROR" />
	</root>

</configuration>
```

In this lesson, you will learn about using Logback.

Introduction to UI Test Automation

Selenium WebDriver Basics

TestNG Framework

Build Management

Configuration Management

Logging

Reporting

Designing the UI Test Automation Framework

Sample UI Test Framework

Using Logback

Logback #

Dependency to add #