Fixtures for browser setup/teardown in Selenium Python - Build an Automation Script

Automate browser setup and teardown using fixtures

Preconditions (4)

Step 1: Create a pytest fixture that opens a Chrome browser before each test

Step 2: Navigate to 'https://example.com' in the browser

Step 3: Verify the page title contains 'Example Domain'

Step 4: Close the browser after the test completes

✅ Expected Result: The browser opens, navigates to the page, verifies the title, and closes cleanly after the test

Automation Requirements - pytest with Selenium WebDriver

Assertions Needed:

Verify page title contains 'Example Domain'

Best Practices:

Use pytest fixtures for setup and teardown

Use explicit waits if needed

Keep test code clean and readable

Close browser in teardown to avoid resource leaks

Automated Solution

Selenium Python

import pytest
from selenium import webdriver
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.common.by import By
from selenium.webdriver.chrome.options import Options

@pytest.fixture
def browser():
    options = Options()
    options.add_argument('--headless=new')  # Run headless for faster tests
    service = Service()  # Assumes chromedriver is in PATH
    driver = webdriver.Chrome(service=service, options=options)
    yield driver
    driver.quit()


def test_example_domain_title(browser):
    browser.get('https://example.com')
    title = browser.title
    assert 'Example Domain' in title, f"Expected 'Example Domain' in title but got '{title}'"

The browser fixture sets up the Chrome browser before the test and closes it after the test finishes using yield. This ensures clean setup and teardown.

The test test_example_domain_title uses the fixture to open the page and then asserts the page title contains the expected text.

Running Chrome in headless mode speeds up tests and avoids opening a visible window.

This structure keeps tests clean, reusable, and avoids resource leaks by closing the browser after each test.

Common Mistakes - 3 Pitfalls

Not closing the browser after the test

Creating the browser inside the test instead of a fixture

Not using headless mode during automated tests

Bonus Challenge

Modify the fixture to accept a browser name parameter to run tests on Chrome and Firefox

Show Hint

Practice

1. What is the main purpose of using a fixture for browser setup and teardown in Selenium tests?

easy

A. To avoid using assertions in tests

B. To write test cases faster without any setup

C. To automate opening and closing the browser before and after tests

D. To run tests only on one browser type

Solution

1. Step 1: Understand fixture role

   Fixtures help prepare the environment before tests and clean up after tests.

2. Step 2: Apply to browser context

   In Selenium, this means opening the browser before tests and closing it after.

3. Final Answer:

   To automate opening and closing the browser before and after tests -> Option C

4. Quick Check:

   Fixture = setup + teardown automation [OK]

Hint: Fixtures handle setup and cleanup automatically [OK]

Common Mistakes:

• Thinking fixtures replace test cases
• Believing fixtures remove need for assertions
• Assuming fixtures limit browser types

2. Which of the following is the correct way to define a pytest fixture for browser setup and teardown using yield?

easy

A. def browser():
driver = webdriver.Chrome()
yield driver
driver.quit()

B. def browser():
driver = webdriver.Chrome()
driver.quit()
yield driver

C. def browser():
yield webdriver.Chrome()
driver.quit()

D. def browser():
driver = webdriver.Chrome()
driver.close()
yield driver

Solution

1. Step 1: Understand yield usage in fixtures

   Yield separates setup (before yield) and teardown (after yield).

2. Step 2: Check correct order

   Setup: create driver; yield it; teardown: quit driver.

3. Final Answer:

   def browser(): driver = webdriver.Chrome() yield driver driver.quit() -> Option A

4. Quick Check:

   Setup before yield, teardown after yield [OK]

Hint: Setup before yield, teardown after yield in fixture [OK]

Common Mistakes:

• Calling quit before yield
• Using driver.close() instead of driver.quit() for teardown
• Yielding before creating driver

3. Given this fixture and test code, what will be printed when the test runs?

import pytest
from selenium import webdriver

@pytest.fixture
def browser():
    driver = webdriver.Chrome()
    print('Setup browser')
    yield driver
    print('Teardown browser')
    driver.quit()

def test_example(browser):
    print('Running test')

medium

A. Running test only

B. Running test\nSetup browser\nTeardown browser

C. Setup browser\nTeardown browser\nRunning test

D. Setup browser\nRunning test\nTeardown browser

Solution

1. Step 1: Trace fixture execution order

   Fixture runs setup code before yield, then test runs, then fixture runs teardown after yield.

2. Step 2: Match print statements order

   Prints 'Setup browser', then 'Running test', then 'Teardown browser'.

3. Final Answer:

   Setup browser\nRunning test\nTeardown browser -> Option D

4. Quick Check:

   Setup -> Test -> Teardown order [OK]

Hint: Fixture setup prints before test, teardown prints after [OK]

Common Mistakes:

• Assuming teardown runs before test
• Ignoring yield separates setup and teardown
• Thinking prints run all before test

4. What is wrong with this fixture code for browser setup and teardown?

@pytest.fixture
def browser():
    driver = webdriver.Chrome()
    driver.quit()
    yield driver

medium

A. Missing import statement for webdriver

B. Calling driver.quit() before yield closes browser too early

C. Yield should be inside a try-except block

D. Fixture should return driver instead of yield

Solution

1. Step 1: Analyze order of operations

   driver.quit() is called before yield, so browser closes before test uses it.

2. Step 2: Understand yield role

   Yield should come before teardown to keep browser open during test.

3. Final Answer:

   Calling driver.quit() before yield closes browser too early -> Option B

4. Quick Check:

   Teardown must be after yield [OK]

Hint: Teardown code must be after yield in fixture [OK]

Common Mistakes:

• Calling quit before yield
• Confusing yield with return
• Ignoring fixture import requirements

5. You want to run multiple tests using the same browser instance to save time. How should you modify the fixture to achieve this?

hard

A. Change fixture scope to 'module' so browser opens once per module

B. Add driver.quit() before yield to close browser early

C. Remove yield and return driver directly

D. Create a new fixture for each test to isolate browser

Solution

1. Step 1: Understand fixture scopes

   Default scope is 'function' which runs fixture per test; 'module' runs once per file.

2. Step 2: Apply scope to reuse browser

   Setting scope='module' opens browser once for all tests in module, saving time.

3. Final Answer:

   Change fixture scope to 'module' so browser opens once per module -> Option A

4. Quick Check:

   Fixture scope controls reuse [OK]

Hint: Use scope='module' to share browser across tests [OK]

Common Mistakes:

• Closing browser before tests run
• Removing yield breaks setup/teardown
• Creating new fixture per test wastes time