Unexpected alert handling in Selenium Java - Framework Patterns

Framework Mode - Unexpected alert handling

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── AlertHandler.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown for browsers.
• Page Objects: Classes representing web pages with methods to interact with UI elements.
• Tests: Test classes containing test methods using assertions to verify behavior.
• Utilities: Helper classes like AlertHandler to manage unexpected alerts safely.
• Configuration: Central place for environment settings, browser options, and credentials.

Configuration Patterns

• Use TestConfig.java to store environment URLs, browser types, and timeout values.
• Use Java properties files or environment variables to keep sensitive data like credentials outside code.
• Configure WebDriver to handle unexpected alerts by setting timeouts and using explicit waits.
• Allow switching browsers via config to run tests on Chrome, Firefox, etc.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports to show test pass/fail results clearly.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests automatically on code changes.
• Include screenshots or logs when unexpected alerts are handled to help debugging.
• Generate HTML or XML reports summarizing alert handling success and failures.

Best Practices

• Always catch UnhandledAlertException in tests or utilities to avoid test crashes.
• Use a dedicated AlertHandler utility class to check for and accept/dismiss alerts safely.
• Do not ignore alerts silently; log alert text for traceability.
• Use explicit waits to wait for alerts before interacting to avoid flaky tests.
• Keep alert handling code reusable and separate from test logic for clarity.

Self Check

Where in this folder structure would you add a new utility class to handle unexpected alerts?

Key Result

Separate alert handling into a reusable utility layer to manage unexpected alerts gracefully without test failures.