Handling hidden elements in Selenium Java - Framework Patterns

Framework Mode - Handling hidden elements

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   ├── LoginPage.java
                │   ├── DashboardPage.java
                ├── tests/
                │   ├── LoginTest.java
                │   ├── HiddenElementTest.java
                ├── utils/
                │   ├── WaitUtils.java
                │   ├── DriverFactory.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., DriverFactory.java).
• Page Objects: Encapsulate page elements and actions (e.g., LoginPage.java). Includes methods to handle hidden elements using explicit waits and JavaScript.
• Tests: Test classes that use page objects to perform test scenarios (e.g., HiddenElementTest.java).
• Utilities: Helper classes for waits, JavaScript execution, and common actions (e.g., WaitUtils.java).
• Configuration: Holds environment settings, browser options, and credentials (e.g., TestConfig.java).

Configuration Patterns

• Environment Properties: Use property files or Java classes (TestConfig.java) to store URLs, credentials, and environment-specific data.
• Browser Settings: Configure browser type and options in DriverFactory.java, allowing tests to run on different browsers.
• Handling Hidden Elements: Use explicit waits (WebDriverWait) with ExpectedConditions.visibilityOfElementLocated or JavaScript to interact with hidden elements.
• Credentials Management: Store sensitive data securely, e.g., environment variables or encrypted files, accessed via config classes.

Test Reporting and CI/CD Integration

• TestNG Reports: Use TestNG's built-in HTML reports for test execution results.
• Logging: Integrate logging (e.g., Log4j) to capture detailed test steps and hidden element handling attempts.
• CI/CD Integration: Configure Jenkins or GitHub Actions to run tests on code commits, with reports archived and notifications sent on failures.
• Screenshot on Failure: Capture screenshots when hidden element interactions fail to help debugging.

Best Practices for Handling Hidden Elements

1. Use Explicit Waits: Always wait for elements to be visible or clickable before interacting to avoid stale or hidden element errors.
2. JavaScript Executor: When elements are hidden but need interaction, use JavaScript to click or set values safely.
3. Page Object Methods: Encapsulate hidden element handling inside page object methods to keep tests clean and reusable.
4. Avoid Thread.sleep(): Never use fixed waits; rely on dynamic waits to improve test speed and reliability.
5. Clear Error Messages: Provide meaningful exceptions or logs when hidden element interactions fail to ease troubleshooting.

Self Check

Where in this folder structure would you add a new method to safely click a hidden button on the Dashboard page?

Key Result

Use explicit waits and JavaScript in page objects to handle hidden elements safely.