How sumit5426/selenium-hybrid-finkraft works
Project Type and Purpose
• This is an open-source, hybrid Selenium Test Automation Framework built in Java 17.
• Purpose: To run UI tests against a web application using TestNG, with data-driven and modular approaches, cloud execution (LambdaTest), parallel runs, detailed logging (Log4j), and rich HTML reports (ExtentReports), all orchestrated by Maven and CI/CD via GitHub Actions.
File Structure
• Top-Level Files
• pom.xml (Maven build & dependency management)
• testng.xml (TestNG suite configuration)
• .github/workflows/maven.yml (CI via GitHub Actions)
• config/ (DEV, QA, UAT .properties + config.json)
• TestData/ (Excel, JSON, CSV test data)
• reports.html, test-output/ (generated reports)
• Source Tree (src/test/java)
• Constants (Browser, Env, Size)
• pages (Page Object Model classes)
• uipojo (POJO classes for Config, Environment, TestData, User)
• uidataprovider (TestNG @DataProvider implementations)
• uilistener (TestNG Listeners: retry analyzer, report listener)
• uiutility (helpers: BrowserUtility, ExcelReader, JsonUtility, PropertiesUtil, LambdaTestUtility, LoggerUtility, ExtentReportUtility)
• uitest (Test classes and TestBase)
• Resources
• src/test/resources/log4j2.xml (logging config)
README for Additional Insights
• Design Patterns: Page Object Model, Singleton, POJO for test data
• Data Handling: Excel, CSV, JSON, Properties; Faker for dynamic data
• Execution Params: isHeadless, isLambdaTest, environmentName, browser
• Cloud: LambdaTest integration
• Reporting: ExtentReports + Log4j
• CI/CD: GitHub Actions scheduled nightly, reports published on gh-pages
a. Main Components
1. CI/CD Layer
• GitHub Actions Workflow (maven.yml)
• Triggers: push, schedule (11:30 PM IST)
2. Build & Orchestration
• Maven Surefire Plugin & TestNG (testng.xml)
3. Test Execution Layer
• TestNG Engine
• Test Classes (uitest/*.java)
• TestBase (initializes WebDriver & environment)
4. Page Object Layer
• pages/*.java (HomePage, LoginPage, FlightInvoicePage)
5. Data Layer
• Test Data Files (Excel, JSON, CSV, Properties)
• Data Providers (uidataprovider/*.java)
• POJOs (uipojo/*.java)
6. Utility Layer
• BrowserUtility (local & remote sessions)
• LambdaTestUtility (cloud)
• ExcelReaderUtility, JsonUtility, PropertiesUtil
• Faker integration (dynamic data)
• LoggerUtility (Log4j)
• ExtentReportUtility
7. Reporting & Logging
• ExtentReports HTML (reports.html, test-output/)
• Log4j logs (./logs/)
8. External System Under Test (SUT)
• Target web application (URL configured via config files)
b. Relationships & Interactions
• GitHub Actions → Maven → TestNG → TestBase
• TestBase → BrowserUtility / LambdaTestUtility → WebDriver Session
• Test Classes → Page Objects → WebDriver → SUT
• Test Classes → Data Providers → POJOs → Data Files
• Utilities (Excel/JSON/Properties) support Data Providers
• Listeners (TestListener, RetryAnalyzer) hook into TestNG events → LoggerUtility + ExtentReportUtility
• Reports & logs are archived and published via GitHub Pages
c. Architectural Patterns & Principles
• Layered Architecture: Clear separation between test logic, page representation, data handling, and utilities
• Modularity: Each functionality in its own package (pages, utilities, listeners)
• Data-Driven: Test data abstracted from test code using POJOs & DataProviders
• Design Patterns: POM for UI, Singleton for driver & report instances, POJO for test data
• CI/CD: Automated test trigger and report publication
d. Key Technologies
• Java 17, Maven, TestNG
• Selenium WebDriver (local & LambdaTest)
• Apache POI, OpenCSV, Gson (data parsing)
• Faker (dynamic test data)
• Log4j2, ExtentReports
• GitHub Actions, gh-pages