Selenium components (WebDriver, Grid, IDE) in Selenium Python - Framework Patterns

Framework Mode - Selenium components (WebDriver, Grid, IDE)

Folder Structure of a Selenium Python Test Project

selenium-python-project/
├── tests/
│   ├── test_login.py
│   ├── test_search.py
│   └── __init__.py
├── pages/
│   ├── login_page.py
│   ├── search_page.py
│   └── __init__.py
├── utils/
│   ├── driver_factory.py
│   ├── config_reader.py
│   └── __init__.py
├── resources/
│   ├── config.yaml
│   └── test_data.json
├── reports/
│   └── latest_report.html
├── conftest.py
├── requirements.txt
└── README.md
  

Test Framework Layers

• Driver Layer: Manages WebDriver instances for browsers. Uses driver_factory.py to create WebDriver objects (local or remote via Selenium Grid).
• Page Objects: Classes representing web pages (e.g., login_page.py). Encapsulate locators and actions for UI elements.
• Test Layer: Contains test scripts (e.g., test_login.py) that use page objects and driver layer to perform test scenarios.
• Utilities: Helper modules like configuration readers, logging, and data handling.
• Configuration: Files like config.yaml hold environment settings, browser choices, and credentials.

Configuration Patterns

Use a config.yaml file to store environment URLs, browser types, Selenium Grid hub URL, and credentials.

# Example config.yaml
environment: "staging"
browser: "chrome"
grid_url: "http://localhost:4444/wd/hub"
credentials:
  username: "testuser"
  password: "password123"
  

Load this config in config_reader.py and pass settings to driver_factory.py to create local or remote WebDriver instances.

Test Reporting and CI/CD Integration

• Use pytest with plugins like pytest-html to generate readable HTML reports saved in reports/.
• Integrate tests in CI/CD pipelines (e.g., GitHub Actions, Jenkins) to run tests on code changes automatically.
• Configure Selenium Grid to run tests in parallel on multiple browsers and machines, speeding up test execution.

Best Practices for Selenium Framework

• Use Page Object Model: Keep locators and page actions in separate classes to improve maintainability.
• Explicit Waits: Use Selenium explicit waits to handle dynamic page elements instead of fixed sleeps.
• Data-Driven Testing: Separate test data from test scripts using JSON or YAML files.
• Use Selenium Grid: Run tests in parallel on different browsers and machines to save time.
• Keep Tests Independent: Each test should set up and clean up its own state to avoid flaky tests.

Self Check Question

Where in this folder structure would you add a new page object class for the "Dashboard" page?

Key Result

Organize Selenium tests using Page Object Model, driver management, config files, and parallel execution with Selenium Grid.