Nested frames in Selenium Java - Framework Patterns

Framework Mode - Nested frames

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   ├── BasePage.java
                │   ├── MainFramePage.java
                │   ├── NestedFramePage.java
                │   └── ...
                ├── tests/
                │   ├── BaseTest.java
                │   ├── NestedFramesTest.java
                │   └── ...
                ├── utils/
                │   ├── DriverFactory.java
                │   ├── WaitUtils.java
                │   └── ConfigReader.java
                └── resources/
                    ├── config.properties
                    └── testdata/
                        └── nested_frames_data.csv

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (DriverFactory.java).
• Page Objects: Classes representing pages or frames (MainFramePage.java, NestedFramePage.java). Each encapsulates frame switching and element interactions.
• Test Layer: Test classes (NestedFramesTest.java) containing test methods using page objects to perform actions and assertions.
• Utilities: Helper classes for waits (WaitUtils.java), configuration reading (ConfigReader.java), and common reusable methods.
• Resources: Configuration files and test data for data-driven testing.

Configuration Patterns

• Environment Config: Use config.properties to store URLs, browser types, timeouts.
• Browser Selection: DriverFactory reads config to initialize Chrome, Firefox, or Edge WebDriver.
• Credentials & Sensitive Data: Store securely outside source code or use environment variables; ConfigReader supports loading.
• Frame Identifiers: Store frame names or IDs in page objects or config for easy maintenance.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports for pass/fail summary.
• Integrate with Allure or ExtentReports for detailed HTML reports with screenshots on failure.
• Configure CI pipelines (Jenkins, GitHub Actions) to run tests on code push, report results, and notify team.
• Include logs for frame switching steps to help debug nested frame issues.

Best Practices for Nested Frames Testing Framework

1. Use Page Object Model: Create separate page objects for each frame level to isolate frame switching logic.
2. Explicit Waits: Use explicit waits before switching frames to ensure frames are loaded.
3. Clear Frame Switching: Always switch back to default content before switching to another frame to avoid stale context.
4. Data-Driven Tests: Use external data files to test different frame scenarios without code changes.
5. Reusable Utilities: Centralize frame switching and wait utilities to avoid duplication.

Self Check

Where in this folder structure would you add a new page object class for a third-level nested frame?

Key Result

Organize nested frame tests using layered Page Objects with clear frame switching and configuration management.