How sadiqmalik8/hybridframework works
Project type and purpose
• This is a Java-based Selenium test-automation framework using the Page Object Model (POM) pattern.
• It automates end-to-end tests against the SwagLabs.com web application.
• Key features: TestNG test runner, POM classes for pages, Excel-driven data (Apache POI), ExtentReports, Log4j logging.
File structure
• Top-level directory “SeleniumPOM” holds all code, drivers, configs, test output.
• src/main/java/SwagLabs:
• Base: BaseClass.java (initializes WebDriver, loads config)
• Config: config.properties (URL, credentials, timeouts)
• Pages: one class per page (LoginPage, HomePage, CartPage, CheckoutPage)
• Utility: WebEventListener, UtilityClass (common helper methods), ExtentReporter
• TestData: Excel file for data-driven tests
• src/main/resources: Log4j config, TestNG suite XMLs
• src/test/java/SwagLabs/TestCases: TestNG test classes invoking POM methods
• chromedriver.exe & geckodriver.exe for WebDriver bindings
• test-output & target: generated reports, logs, compiled classes
README
• Confirms POM design, Apache POI, Extent Report, Log4j
• Indicates the AUT is SwagLabs.com
a. Main components
1. Test Runner Layer: TestNG suites (testng.xml/testng_sanity.xml)
2. Configuration Layer: config.properties, Log4j
3. Base Framework Layer: BaseClass (WebDriver init), WebEventListener
4. Page Object Layer: LoginPage, HomePage, CartPage, CheckoutPage
5. Test Data Layer: Excel sheet (Apache POI)
6. Utility & Reporting Layer: UtilityClass, ExtentReporter
7. External/Infrastructure: ChromeDriver/GeckoDriver, Browser, SwagLabs web app
8. Output Layer: TestNG reports, ExtentReports, logs in test-output folder
b. Relationships and data flow
• BaseClass reads config.properties → initializes WebDriver & listeners
• Test Cases call methods on Page Object classes → page objects use WebDriver to drive the browser
• Page Objects fetch test data from Excel via UtilityClass → data passed into page actions
• After each test, ExtentReporter & Log4j capture events → generate HTML/JS/CSS reports in test-output
• WebDriver interacts with AUT (SwagLabs.com) over HTTP
c. Architectural patterns & principles
• Page Object Model (separation of page locators and tests)
• Single Responsibility: each class has one role (config loader, driver manager, test case, reporter)
• Data-Driven Testing (Excel + Apache POI)
• Observer/Listener Pattern: WebEventListener intercepts WebDriver events
d. Technologies & frameworks
• Selenium WebDriver (browser automation)
• Java + TestNG (test framework)
• Apache POI (Excel reading)
• ExtentReports (rich HTML reporting)
• Log4j (logging)
• Maven (build & dependency management)