How prajwalsolanke23/uem_automation_testng_framework works
This project is a hybrid TestNG automation framework that combines several design patterns and testing strategies such as the Page Object Model, Page Factory, and Data-Driven Testing with Apache POI Excel integration. The file structure and README indicate that it’s built as a Maven project with a layered architecture aimed at automating UI testing scenarios, likely for a web (or desktop) application.
Overall Project Layers
• Build & Project Management: Represented by Maven (pom.xml, .mvn directory) which handles dependencies, build lifecycle, and configuration.
• Configuration Management: The “config” package (config/config.properties) contains the configurable parameters (URL, device, group, etc.).
• Test Execution Framework: Use TestNG as the test runner which is configured via the testng.xml file under src/test/resources and supports test execution, grouping, and reports.
• Reporting & Logging: Illustrated by the Extent Reporting integration (ExtentReporter.java) and any logging utilities used in the framework.
Core Functional Components
a. Page Object Layer:
• Pages: Under src/main/java/com/uem_automation/qa/pages, you have classes like AdministrationSettingsPage, LoginPage, TaskManagerPage, etc. Each page class embodies the UI elements and actions for their respective parts of the application.
• Design Pattern: The use of Page Factory design pattern is indicated as well, enabling cleaner separation and initialization of page elements.
b. Test Data Handling:
• Test Data: The “testdata” folder in src/main/java/com/uem_automation/qa/testdata holds Excel files, installers, and other data assets, crucial for data-driven testing and scenarios.
c. Listeners and Test Hooks:
• Test Listeners: Located under src/main/java/com/uem_automation/qa/listeners, these classes (e.g., MyListeners.java) capture test status, integrate with reports, or handle additional test events.
d. Utility and Support Components:
• Utility Classes: Under src/main/java/com/uem_automation/qa/utils, there are utility classes (Utilities.java) and reporting helpers that support the main testing functionality.
Test Cases and Experimentation
• Test Cases: Found under src/test/java/com/uem_automation/qa/testcases (e.g., LoginTest, TaskManagerTest, DeviceManagerWindowsTest) which call upon the Page Objects to execute test scenarios.
• Experimentation: The experiments package under src/test/java/experiments is used for trying out additional code or assertions (like reading Excel or handling date-time stamps).
Relationships and Interactions
• The TestNG test suite (configured via testng.xml) initiates test execution.
• Each test case utilizes one or more Page Object classes to interact with the application's UI.
• The Page Object classes load configurations from the config layer and use utilities (possibly including Apache POI for Excel parsing) to drive data.
• Listeners capture runtime events (successes/failures) and feed information into the reporting framework (Extent Reports).
• Maven handles building, compiling, and packaging of the test framework, while output reports and logs are stored in the “target” and “test-output” directories.