Data providers pattern in Selenium Python - Framework Patterns

Framework Mode - Data providers pattern

Folder Structure

my_selenium_project/
├── tests/
│   ├── test_login.py          # Test files using data providers
│   └── test_search.py
├── pages/
│   ├── login_page.py          # Page Object classes
│   └── search_page.py
├── data/
│   └── test_data.py           # Data provider functions or data sets
├── utils/
│   └── helpers.py             # Utility functions
├── config/
│   └── config.py              # Environment and browser configs
├── conftest.py                # Pytest fixtures and hooks
└── requirements.txt

Test Framework Layers

• Test Layer: Contains test scripts that use data providers to run tests multiple times with different inputs.
• Page Object Layer: Classes representing web pages with methods to interact with UI elements.
• Data Provider Layer: Functions or variables that supply test data, often in data/test_data.py.
• Utility Layer: Helper functions for common tasks like reading files or formatting data.
• Configuration Layer: Holds environment settings, browser options, and credentials.
• Fixtures: In conftest.py, setup and teardown logic, including browser setup.

Configuration Patterns

• Environment Config: Use config/config.py to define URLs, timeouts, and environment variables.
• Browser Config: Parameterize browser choice via command line or config file, e.g., Chrome or Firefox.
• Credentials: Store sensitive data securely, e.g., environment variables or encrypted files, not hardcoded.
• Data Providers: Keep test data separate from tests, load from data/test_data.py or external files (CSV, JSON).
• Pytest Integration: Use fixtures and @pytest.mark.parametrize to connect data providers with tests.

Test Reporting and CI/CD Integration

• Use pytest with plugins like pytest-html or allure-pytest for readable test reports showing which data sets passed or failed.
• Integrate tests into CI/CD pipelines (GitHub Actions, Jenkins) to run tests automatically on code changes.
• Reports help quickly identify which input data caused failures.
• Use logs and screenshots on failure for easier debugging.

Best Practices

• Separate Data from Tests: Keep test data in dedicated files or functions, not inside test scripts.
• Use Pytest Parametrize: Leverage @pytest.mark.parametrize to run tests with multiple data sets cleanly.
• Readable Data Format: Use simple structures like lists of tuples or dictionaries for data providers.
• Maintainable Data: Organize data logically by test case or feature for easy updates.
• Secure Sensitive Data: Never hardcode passwords or secrets in data providers; use environment variables.

Self Check

Where in this folder structure would you add a new data provider for testing the "Forgot Password" feature?

Key Result

Use separate data provider functions or files to supply multiple test inputs, combined with pytest parametrize for clean, reusable test automation.