Why test frameworks structure execution in Selenium Python - Framework Benefits

Framework Mode - Why test frameworks structure execution

Folder Structure

selenium-python-project/
├── tests/
│   ├── test_login.py
│   ├── test_checkout.py
│   └── __init__.py
├── pages/
│   ├── login_page.py
│   ├── checkout_page.py
│   └── __init__.py
├── utils/
│   ├── driver_factory.py
│   ├── wait_helpers.py
│   └── __init__.py
├── config/
│   ├── config.yaml
│   └── __init__.py
├── reports/
│   └── latest_report.html
├── conftest.py
└── pytest.ini

Test Framework Layers

• Driver Layer: Manages browser setup and teardown using Selenium WebDriver (e.g., driver_factory.py).
• Page Objects: Encapsulate page elements and actions (e.g., login_page.py).
• Test Cases: Actual test scripts using PyTest in tests/ folder.
• Utilities: Helper functions like waits, logging, and data handling.
• Configuration: Environment settings, URLs, credentials stored in config.yaml.

Configuration Patterns

Use a config.yaml file to store environment URLs, browser types, and credentials. Load these settings in conftest.py to provide fixtures for tests.

Example config.yaml snippet:

environment:
  url: "https://testsite.com"
  browser: "chrome"
credentials:
  username: "testuser"
  password: "password123"

This allows easy switching between test, staging, and production environments without changing code.

Test Reporting and CI/CD Integration

Use PyTest's built-in reporting with plugins like pytest-html to generate readable HTML reports saved in the reports/ folder.

Integrate the test suite with CI/CD tools (e.g., GitHub Actions, Jenkins) to run tests automatically on code changes. Reports help quickly see pass/fail results.

Best Practices

• Clear Separation: Keep page objects, tests, and utilities separate for easy maintenance.
• Reusable Components: Use page objects and utility functions to avoid repeating code.
• Configurable Settings: Store environment and browser info outside code for flexibility.
• Explicit Waits: Use waits to handle dynamic page loading and avoid flaky tests.
• Readable Reports: Generate clear test reports to understand results quickly.

Self Check

Where in this folder structure would you add a new page object for the user profile page?

Key Result

Test frameworks structure execution by separating concerns into layers like page objects, tests, utilities, and config to improve maintainability and clarity.

Practice

1. Why do test frameworks structure test execution with setup and teardown steps?

easy

A. To prepare and clean the test environment automatically for each test

B. To make tests run slower and harder to manage

C. To skip tests that are not important

D. To write tests without any code

Solution

1. Step 1: Understand setup and teardown roles

   Setup prepares the environment before a test, and teardown cleans up after it.

2. Step 2: Recognize automation benefits

   Automating these steps ensures tests run reliably and independently without manual work.

3. Final Answer:

   To prepare and clean the test environment automatically for each test -> Option A

4. Quick Check:

   Setup and teardown automate environment prep = D [OK]

Hint: Setup/teardown automate prep and cleanup [OK]

Common Mistakes:

• Thinking setup slows tests
• Believing tests run without code
• Confusing skipping tests with setup

2. Which of the following is the correct way to define a setup method in a pytest test class?

easy

A. def setup(self):

B. def setup_method(self, method):

C. def setUp(self):

D. def Setup(self):

Solution

1. Step 1: Recall pytest setup naming conventions

   Pytest uses setup_method(self, method) for setup before each test method.

2. Step 2: Check other options for correctness

   Options A and D have wrong names or casing; B is unittest style, not pytest.

3. Final Answer:

   def setup_method(self, method): -> Option B

4. Quick Check:

   Pytest setup method = setup_method [OK]

Hint: Pytest uses setup_method for setup in classes [OK]

Common Mistakes:

• Using unittest setup names in pytest
• Wrong method name casing
• Missing method parameter 'method'

3. Given this pytest code snippet, what will be the output when running the tests?

import pytest

class TestExample:
    def setup_method(self):
        print('Setup')

    def teardown_method(self):
        print('Teardown')

    def test_one(self):
        print('Test One')
        assert True

    def test_two(self):
        print('Test Two')
        assert True

medium

A. Setup\nTest One\nTeardown\nSetup\nTest Two\nTeardown

B. Test One\nTest Two

C. Setup\nTeardown\nSetup\nTeardown

D. Setup\nTest One\nTest Two\nTeardown

Solution

1. Step 1: Understand pytest setup/teardown per test

   setup_method runs before each test, teardown_method after each test.

2. Step 2: Trace print statements in order

   For test_one: Setup, Test One, Teardown; for test_two: Setup, Test Two, Teardown.

3. Final Answer:

   Setup\nTest One\nTeardown\nSetup\nTest Two\nTeardown -> Option A

4. Quick Check:

   Setup and teardown run before/after each test = A [OK]

Hint: Setup/teardown print around each test method [OK]

Common Mistakes:

• Assuming setup runs once for all tests
• Missing teardown prints
• Thinking tests run without setup/teardown

4. You wrote this pytest test class but the setup method is not running before tests. What is the error?

class TestSample:
    def setup(self):
        print('Setup running')

    def test_check(self):
        assert True

medium

A. Missing self parameter in setup method

B. Test method name should start with 'check_'

C. Method name should be setup_method, not setup

D. setup method must return True

Solution

1. Step 1: Identify pytest setup method naming

   Pytest expects setup_method(self) for setup before each test method.

2. Step 2: Check method name correctness

   Using 'setup' alone is not recognized by pytest, so setup is not called.

3. Final Answer:

   Method name should be setup_method, not setup -> Option C

4. Quick Check:

   Pytest setup method must be setup_method [OK]

Hint: Use setup_method for pytest setup in classes [OK]

Common Mistakes:

• Using unittest setup name in pytest
• Forgetting 'self' parameter
• Wrong test method naming

5. In a Selenium test framework, why is structuring tests with setup and teardown important when running many tests in a suite?

hard

A. It skips tests that fail to save time

B. It makes tests run in random order to find bugs

C. It allows tests to share browser state for speed

D. It ensures each test starts fresh and cleans up, preventing side effects

Solution

1. Step 1: Understand test isolation importance

   Each test should run independently to avoid interference from others.

2. Step 2: Recognize setup/teardown role in isolation

   Setup prepares a clean state; teardown cleans resources so tests don't affect each other.

3. Final Answer:

   It ensures each test starts fresh and cleans up, preventing side effects -> Option D

4. Quick Check:

   Setup/teardown keep tests isolated and clean = A [OK]

Hint: Setup/teardown keep tests independent and clean [OK]

Common Mistakes:

• Thinking tests share browser state for speed
• Believing tests run randomly by setup
• Assuming failing tests are skipped automatically