Opening URLs (driver.get) in Selenium Java - Framework Patterns

Framework Mode - Opening URLs (driver.get)

Folder Structure

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

Test Framework Layers

• Driver Layer: Manages WebDriver instances (e.g., WebDriverFactory.java). Responsible for browser setup and teardown.
• Page Objects: Classes representing web pages (e.g., HomePage.java). Contains locators and methods to interact with page elements, including opening URLs using driver.get().
• Tests: Test classes (e.g., HomePageTest.java) that use page objects to perform test scenarios and assertions.
• Utilities: Helper classes for common tasks like reading configuration or waiting for elements.
• Configuration: Classes or files to manage environment settings, URLs, and credentials (e.g., ConfigReader.java).

Configuration Patterns

• Environment Properties: Use a properties file (e.g., config.properties) to store URLs, browser types, and credentials.
• ConfigReader Class: Reads properties and provides access to environment-specific URLs.
• Browser Selection: Pass browser type as a parameter or system property to WebDriverFactory to open different browsers.
• URL Management: Store base URLs in config and use them in page objects or tests to open pages with driver.get().

Test Reporting and CI/CD Integration

• TestNG Reports: Use TestNG's built-in HTML reports to see test execution results.
• Logging: Add logging to track when URLs are opened with driver.get().
• CI/CD Integration: Integrate tests in Jenkins or GitHub Actions to run on code commits, reporting pass/fail status.
• Screenshot on Failure: Capture screenshots if opening a URL fails or page does not load.

Best Practices

1. Use Page Object Model: Encapsulate driver.get() calls inside page object constructors or methods for better maintainability.
2. Explicit Waits: After opening a URL, wait explicitly for key elements to load before interacting.
3. Centralize URLs: Store all URLs in configuration files to avoid hardcoding in tests or page objects.
4. Browser Factory: Use a factory pattern to create WebDriver instances to support multiple browsers easily.
5. Clean Setup and Teardown: Initialize and quit WebDriver properly in test setup and teardown methods to avoid resource leaks.

Self Check

Where in this folder structure would you add a new page object class for a login page that needs to open its URL using driver.get()?

Key Result

Use Page Object Model with centralized configuration and WebDriver factory to open URLs cleanly and reliably.