DEV Community: Jeissy Guimarães

Building a Test Automation Architecture with Java, Selenium, Maven, Docker, and Jenkins CI/CD

Jeissy Guimarães — Sun, 04 Aug 2024 23:13:52 +0000

Overview

In today's fast-paced development environment, maintaining a robust test automation architecture is crucial. Our project, selenium_java_test_automation_ach, is designed to streamline automated testing using Java, Selenium, Maven, Docker, and Jenkins CI/CD. This architecture not only adheres to the SOLID principles but also incorporates best coding practices to ensure maintainable and scalable code.

Project Objectives

🔍 Automated Testing: Implement a comprehensive automated testing solution using Selenium and Java;
📊 Comprehensive Reports: Generate detailed test reports with ExtentReports;
🚀 CI/CD Integration: Ensure seamless integration into CI/CD pipelines using Jenkins;
🌐 Multi-browser Support: Provide support for multiple browsers (Chrome, Firefox, Edge), including headless mode
Key Features;
🖥️ExtentReports for Test Sessions: Initialization and closure of test sessions with ExtentReports, including WebDriver configuration;
📸 Visual Capture and Comparison: Capture and compare screenshots of web pages against a predefined visual baseline;
🔧 WebDriver Configuration: Flexible WebDriver setup supporting multiple browsers and headless mode;
🤖 Selenium Automation: Leverage Selenium to automate browser interactions, page navigations, and checkpoints.

Technologies Used

☕Java: The core programming language for writing test cases;
🌐 Selenium: A powerful tool for browser automation;
🧪 TestNG: Framework for managing and executing tests;
📊 ExtentReports: Library for generating detailed and visual test reports;
✨ Lombok: Utility to reduce boilerplate code;
⚙️ Jenkins: Continuous integration and deployment server;
🐳 Docker: Platform for developing, shipping, and running applications in containers;

SOLID Principles and Best Practices

This project is developed following SOLID principles and best coding practices to ensure a maintainable and scalable foundation:

Single Responsibility Principle: Each class has a single responsibility.
Open/Closed Principle: Classes are open for extension but closed for modification.
Liskov Substitution Principle: Subclasses should replace their base classes without breaking the application.
Interface Segregation Principle: Create specific interfaces for clients, avoiding monolithic interfaces.
Dependency Inversion Principle: Depend on abstractions, not on concrete implementations.

Conclusion

By adhering to the SOLID principles and utilizing best practices, our project ensures a robust, maintainable, and scalable test automation architecture. The combination of Java, Selenium, Maven, Docker, and Jenkins CI/CD streamlines the testing process and provides immediate feedback, making it an ideal solution for modern software development environments.

For more details about the project, visit:
GITHUB

Feel free to explore the project repository for more details and to contribute!

Building Test Automation Architecture with Java, Selenium, Maven, Docker, and Jenkins CI/CD

Jeissy Guimarães — Sun, 04 Aug 2024 22:55:31 +0000

Overview

Project Objectives

🔍 Automated Testing: Implement a comprehensive automated testing solution using Selenium and Java;
📊 Comprehensive Reports: Generate detailed test reports with ExtentReports;
🚀 CI/CD Integration: Ensure seamless integration into CI/CD pipelines using Jenkins;
🌐 Multi-browser Support: Provide support for multiple browsers (Chrome, Firefox, Edge), including headless mode
Key Features;
🖥️ExtentReports for Test Sessions: Initialization and closure of test sessions with ExtentReports, including WebDriver configuration;
📸 Visual Capture and Comparison: Capture and compare screenshots of web pages against a predefined visual baseline;
🔧 WebDriver Configuration: Flexible WebDriver setup supporting multiple browsers and headless mode;
🤖 Selenium Automation: Leverage Selenium to automate browser interactions, page navigations, and checkpoints.

Technologies Used

☕Java: The core programming language for writing test cases;
🌐 Selenium: A powerful tool for browser automation;
🧪 TestNG: Framework for managing and executing tests;
📊 ExtentReports: Library for generating detailed and visual test reports;
✨ Lombok: Utility to reduce boilerplate code;
⚙️ Jenkins: Continuous integration and deployment server;
🐳 Docker: Platform for developing, shipping, and running applications in containers;

SOLID Principles and Best Practices

This project is developed following SOLID principles and best coding practices to ensure a maintainable and scalable foundation:

Single Responsibility Principle: Each class has a single responsibility.
Open/Closed Principle: Classes are open for extension but closed for modification.
Liskov Substitution Principle: Subclasses should replace their base classes without breaking the application.
Interface Segregation Principle: Create specific interfaces for clients, avoiding monolithic interfaces.
Dependency Inversion Principle: Depend on abstractions, not on concrete implementations.

Conclusion

For more details about the project, visit:
GitHub

Visual Test Automation with Python and Applitools: Using Ignore Regions

Jeissy Guimarães — Tue, 16 Jul 2024 14:34:38 +0000

Introduction

Visual test automation is essential to ensure that the user interfaces (UIs) of web applications are correct and visually consistent. By using Applitools, we can perform automated visual comparisons, identifying subtle differences that might be missed in manual tests. A useful feature of Applitools is the ability to define "Ignore Regions" - areas of the page that are ignored during visual comparison, such as dynamic elements that change frequently (e.g., banners, ads, etc.).

In this article, we will explore how to configure and use "Ignore Regions" in automated visual tests with Python and Applitools.

Advantages of Applitools for Layout and Visual Testing

🔍 Visual Difference Detection: Applitools uses AI to detect visual differences that might not be captured by traditional code checks. This is crucial to ensure that the user interface is correct and free from visual regressions.

🔧 Ease of Integration: It can be easily integrated with various test automation tools like Selenium, Cypress, among others. This allows you to add visual checks to your existing test flows without major rewrites.

🛠 Simplified Test Maintenance: With Applitools' "Baseline" approach, it is easy to update and maintain visual tests. When a UI change is intentional, you can update the baseline with a click.

🚫 Ignore Regions: Allows you to specify areas of the page to be ignored during visual comparison. This is useful for dynamic areas that change frequently and are not relevant to the visual test.

Code Implementation EyesLibrary Class The EyesLibrary class manages the integration with Applitools. Let's focus specifically on the function that defines the regions to be ignored during visual tests.

Advantages of the check_window_with_ignore Function

The check_window_with_ignore function is crucial for the robustness of visual tests, allowing specific areas of the page to be ignored. This is particularly useful in scenarios where dynamic elements, such as ads or notifications, can introduce visual variations that are not relevant to the test.

Example of Use

In the login test, we use this functionality to ignore specific elements of the page that might vary between test runs.

Conclusion
By using Applitools with Python, we can efficiently perform automated visual tests. The "Ignore Regions" functionality is especially useful for dynamic areas of the page, ensuring that our visual tests are precise and relevant. With this configuration, you can easily integrate these tests into your CI/CD pipeline, ensuring the continuous visual quality of your application.

For more information, check out the documentation for Applitools

The complete code can be found on GitHub.