Automation Framework

WORK IN PROGRESS

Overview

The purpose of data-driven testing with Selenium automation is to enhance the efficiency, effectiveness, and coverage of your testing efforts by systematically testing your application with multiple sets of input data.

Purpose

Below points are the purposes for using a data-driven testing framework

1. Increased Test coverage

2. Efficiency and Reusability

3. Regression Testing

4. Validation of Input Data

5. Scalability

6. Exploratory Testing Support

7. Parameterization

8. Maintaining Test Data Separately

9. Consistency and Reproducibility

10. Compliance and Regulation Testing

Technologies and tools

1. Selenium WebDriver - This provides a programming interface to interact with web elements and automate tasks in web applications

2. Java -

3. Maven - This is being used as a Dependency Management tool.

4. TestNG - TestNG is used as a framework and as a reporting tool as well.

5. Log4j - It's used to log messages within software and can communicate with other services on a system.

6. Jackson - Java library for parsing and generating JSON, which is part of the FasterXML project and is known for being fast, flexible, and powerful.

7. WebDriverManager - WebDriverManager can automatically download and manage WebDriver dependencies for various browsers, including Chrome, Firefox, Safari, and Edge.

Prerequisites

Test framework setup

Step 1: Set Up a Maven Project

Step 2: Add the below-mentioned Dependencies in pom.xml

• Selenium Webdriver

selenium-java

• TestNG

testng

• Webdriver Manager

webdrivermanager

• log4j

log4j-api

log4j-core

• Jackson

jackson-core

Step 3: Create Data-Driven Test Class

Step 4: Create TestNG XML File

Step 5: Implement Data Provider

Step 6: Execute Tests

Test data preparation

• The test data file format should be JSON.

• JSON format should be proper.

• Any number of data points can be passed.

Test case design

Test scenarios

• Each Page should have its test class, and each scenario should have its method.

• All Sanity and Regression scenarios are to be covered.

• Both scenarios can be run separately.

• Negative scenarios are also covered

Test steps

• Provide both valid and invalid test data in the JSON file

• Provide only the required number of test data to avoid a longer run time.

Data-Driven testing implementation

Test Data Storage: All test inputs are stored in a structured JSON file ( testdata.json).

POJO Class (TestData): A simple Java class with getters and setters maps the JSON fields.

Data Reader Utility: ObjectMapper From Jackson is used to parse the JSON into a list of TestData objects.

Data Provider Method: A TestNG @DataProvider Returns test data as a 2D Object[][] array.

Test Method: The @Test method accepts TestData as a parameter and extracts values via getters.

Reporting and logging

Test result reporting

• TestNG is used as a report provider

• Every class name is to be mentioned in the testng.xml file to be a part of a report

• Should be able to generate an HTML emailable report by running the testng.xml file.

• An emailable-report.html and testing-failed.xml Reports to be generated in the test-output file.

Logging

• Log4j has been used as a logging tool

• This will provide the log for each test method that fails during the test suite execution

• Finding the exact error in the test suite execution will be easy

Test environment configuration

Driver configuration

• Driver configuration will be handled by the Webdriver Manager .

• Webdriver Manager will manage the download, setup, and maintenance of the drivers required by Selenium WebDriver.

Test environment parameters

• Users need to provide the browser name (case-insensitive) and the URL of the environment in configfiles > config.properties.

Maintenance and updates

Test data updates

1. Identify the need for updates, considering application changes, data quality, and new scenarios.

2. Update data in its source (JSON file) to reflect current requirements and formats.

3. Ensure data validity by including boundary and edge cases.

4. Consider versioning data for tracking changes over time.

Codebase maintenance

Conclusion

Future improvements