Test class consuming page objects in Selenium Java - Framework Patterns

Framework Mode - Test class consuming page objects

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   ├── LoginPage.java
                │   └── HomePage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── WebDriverFactory.java
                └── config/
                    └── ConfigReader.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., WebDriverFactory).
• Page Objects: Classes representing web pages with locators and actions (e.g., LoginPage).
• Test Classes: TestNG or JUnit classes that use page objects to perform tests (e.g., LoginTest).
• Utilities: Helper classes for common tasks like reading configs or waiting.
• Configuration: Files and classes to manage environment settings, URLs, credentials.

Configuration Patterns

• Use a config.properties file to store environment URLs, browser types, and credentials.
• ConfigReader class loads properties and provides getters.
• Pass browser type as a system property or environment variable to support multiple browsers.
• Use WebDriverFactory to create WebDriver instances based on config.
• Keep sensitive data like passwords encrypted or use environment variables for security.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports or integrate with Allure for detailed HTML reports.
• Configure test listeners to capture screenshots on failure.
• Integrate tests into CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run tests on code changes.
• Publish reports as build artifacts for easy access.
• Use tags or groups in TestNG to run subsets of tests in CI.

Best Practices

• Page Object Model: Keep locators and page actions inside page classes to separate test logic from UI details.
• Single Responsibility: Each class should have one clear purpose (page, test, utility).
• Explicit Waits: Use waits in page objects to handle dynamic page elements reliably.
• Reusable Components: Avoid duplicating code by creating common methods in base classes or utilities.
• Clear Naming: Name page objects and test classes clearly to reflect their role.

Self Check

Where in this folder structure would you add a new page object class for the "ProfilePage"?

Key Result

Test classes use page objects to interact with the UI, keeping tests clean and maintainable.