Nested iFrames in Selenium Python - Framework Patterns

Framework Mode - Nested iFrames

Folder Structure

nested_iframes_test_project/
├── src/
│   ├── pages/
│   │   ├── base_page.py
│   │   ├── main_page.py
│   │   └── iframe_page.py
│   ├── tests/
│   │   └── test_nested_iframes.py
│   ├── utils/
│   │   ├── driver_factory.py
│   │   └── wait_utils.py
│   └── config/
│       └── config.yaml
├── requirements.txt
└── pytest.ini

Test Framework Layers

• Driver Layer: driver_factory.py creates and manages WebDriver instances with browser options.
• Page Objects: Classes in pages/ represent pages and frames. For nested iFrames, iframe_page.py handles switching between frames.
• Tests: Test scripts in tests/ use page objects to perform actions and assertions on nested iFrames.
• Utilities: Helper functions like explicit waits in wait_utils.py to handle dynamic loading inside iFrames.
• Configuration: config.yaml stores environment URLs, browser types, and credentials.

Configuration Patterns

Use a config.yaml file to store settings:

environment:
  url: "https://example.com/nested_iframes"
browser: "chrome"
implicit_wait: 10
explicit_wait: 15

Load config in driver_factory.py to create WebDriver with chosen browser and wait times.

Use environment variables or command-line options to switch environments or browsers without code changes.

Test Reporting and CI/CD Integration

• Use pytest with pytest-html plugin to generate readable HTML reports after test runs.
• Integrate tests in CI/CD pipelines (GitHub Actions, Jenkins) to run on every code push or pull request.
• Configure test retries and screenshots on failure to help diagnose nested iFrame issues.
• Reports show pass/fail status of tests interacting with nested iFrames clearly.

Best Practices for Nested iFrames Testing Framework

1. Use Page Object Model: Create separate page objects for main page and each iFrame to keep code clean and reusable.
2. Explicit Waits: Always use explicit waits when switching to iFrames to ensure elements inside are loaded.
3. Clear Frame Switching: Always switch back to default content after working inside an iFrame to avoid stale context errors.
4. Isolate Tests: Each test should start with a fresh driver state and navigate to the main page to avoid dependencies.
5. Configurable Settings: Use config files and environment variables to easily change browsers and URLs without code edits.

Self Check

Where in this folder structure would you add a new page object for a third nested iFrame inside the existing iFrame?

Key Result

Organize nested iFrame tests with clear page objects, explicit waits, and config-driven WebDriver setup.