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

### How to control parallelism?

TestNG provides features to run tests in parallel. This parallelism and the thread count can be controlled from ***testng.xml***.

Parallelism and thread count can be set at `suite` level or `test` level like below.

```xml
<suite name="Sample Test Suite" parallel="tests" thread-count="5">
```

```xml
<test name="Sample Test" parallel="tests" thread-count="5">
```

### Types of parallelism
TestNG supports the following parallelism:

* `methods` run test methods in parallel in different threads. All dependent methods will be run in different threads, respecting the priority of tests.
* `tests` run *\<test\>* tags in parallel in separate threads.
* `classes` run test classes in parallel in separate threads, but test methods in those test classes will run in the same thread.
* `instances` run instances of test methods/classes in parallel in different threads.

In the case of `@DataProvider`, the parallelism can be controlled using the attribute `@DataProvider(parallel = true)`. By default, it is set to ***false*** and default dataprovider thread count is **10** which is considered only when parallel is enabled.

---

Now that you are familiar with running tests in parallel, in the next lesson, you will learn about grouping the tests.

# How to control parallelism?

TestNG provides features to run tests in parallel. This parallelism and the thread count can be controlled from ***testng.xml***.

Parallelism and thread count can be set at `suite` level or `test` level like below.

```xml
<suite name="Sample Test Suite" parallel="tests" thread-count="5">
```

```xml
<test name="Sample Test" parallel="tests" thread-count="5">
```

# Types of parallelism
TestNG supports the following parallelism:

* `methods` run test methods in parallel in different threads. All dependent methods will be run in different threads, respecting the priority of tests.
* `tests` run *\<test\>* tags in parallel in separate threads.
* `classes` run test classes in parallel in separate threads, but test methods in those test classes will run in the same thread.
* `instances` run instances of test methods/classes in parallel in different threads.

In the case of `@DataProvider`, the parallelism can be controlled using the attribute `@DataProvider(parallel = true)`. By default, it is set to ***false*** and default dataprovider thread count is **10** which is considered only when parallel is enabled.

---

Now that you are familiar with running tests in parallel, in the next lesson, you will learn about grouping the tests.

In this topic, we will see how to run tests in parallel and how to control the thread count.

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

Conclusion

Running Tests in Parallel

How to control parallelism? #