Creating new windows/tabs in Selenium Java - Framework Setup Guide

Framework Mode - Creating new windows/tabs

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   ├── BasePage.java
                │   ├── HomePage.java
                │   └── NewTabPage.java
                ├── tests/
                │   └── WindowTabTests.java
                ├── utils/
                │   └── WebDriverFactory.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Driver Layer: Manages WebDriver instances and browser setup (e.g., WebDriverFactory.java).
• Page Objects: Encapsulate page elements and actions, including handling multiple windows/tabs (e.g., HomePage.java, NewTabPage.java).
• Tests: Contains test classes that use page objects to perform actions and assertions (e.g., WindowTabTests.java).
• Utilities: Helper classes for common functions like waits, window switching, and test data.
• Configuration: Holds environment settings, browser options, and credentials (e.g., TestConfig.java).

Configuration Patterns

• Environment Properties: Use TestConfig.java or property files to define URLs, browser types, and timeouts.
• Browser Setup: Configure browser options in WebDriverFactory.java to support multiple browsers and headless mode.
• Credentials: Store securely using environment variables or encrypted files, accessed via config classes.
• Window/Tab Handling: Use explicit waits and window handles managed in page objects or utilities to switch between tabs/windows reliably.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports or integrate with Allure for detailed, user-friendly test reports.
• Generate HTML reports after test runs showing pass/fail status and screenshots on failure.
• Integrate tests into CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run tests automatically on code changes.
• Configure parallel test execution with proper WebDriver management to handle multiple windows/tabs in parallel runs.

Best Practices

1. Use Page Object Model: Encapsulate window/tab switching logic inside page objects to keep tests clean.
2. Explicit Waits: Always wait for new windows or tabs to appear before switching to avoid flaky tests.
3. Store Window Handles: Save original window handle before opening new tabs to switch back easily.
4. Clean Up: Close new tabs/windows after tests to avoid resource leaks.
5. Isolate Tests: Each test should open and close its own windows/tabs to avoid interference.

Self Check

Where in this folder structure would you add a new page object class to handle interactions on a newly opened browser tab?

Key Result

Use Page Object Model with explicit waits and window handle management to create and test new windows/tabs in Selenium Java.