Conftest for shared fixtures in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this pytest fixture usage?

Given the following conftest.py fixture and test code, what will be printed when running test_example?

Selenium Python

import pytest

@pytest.fixture(scope="module")
def browser():
    print("Setup browser")
    yield "ChromeDriver"
    print("Teardown browser")

def test_example(browser):
    print(f"Using {browser}")
    assert browser == "ChromeDriver"

A Setup browser\nUsing ChromeDriver\nTeardown browser

B Setup browser\nTeardown browser\nUsing ChromeDriver

C Using ChromeDriver\nSetup browser\nTeardown browser

D Using ChromeDriver only

💡 Hint

Remember that fixtures with yield run setup code before the test and teardown code after.

The fixture runs the setup code first (prints 'Setup browser'), then the test runs (prints 'Using ChromeDriver'), and finally the teardown code runs (prints 'Teardown browser').

❓ assertion

intermediate

Which assertion correctly verifies the fixture value?

Assuming a fixture driver returns a Selenium WebDriver instance, which assertion correctly checks the page title is 'Home'?

Selenium Python

def test_title(driver):
    driver.get('http://example.com')
    # Which assertion is correct here?

A assert driver.page_title == 'Home'

B assert driver.get_title() == 'Home'

C assert driver.title == 'Home'

D assert driver.title() == 'Home'

💡 Hint

Check the Selenium WebDriver API for the page title property.

The correct property to get the page title is driver.title. Methods like get_title() or title() do not exist.

❓ locator

advanced

Which locator is best for a shared fixture to find a login button?

In a shared fixture, you want to locate the login button reliably across tests. Which locator is best practice?

A driver.find_element('class name', 'btn')

B driver.find_element('xpath', '//button[text()="Login"]')

C driver.find_element('css selector', 'button.btn-primary')

D driver.find_element('id', 'login-btn')

💡 Hint

IDs are unique and stable locators.

Using the element's unique ID is the most reliable and fastest locator. Other options may be less stable or ambiguous.

🔧 Debug

advanced

Why does this fixture cause tests to fail intermittently?

Analyze the following fixture and explain why tests using it sometimes fail with a stale element error.

Selenium Python

import pytest

@pytest.fixture(scope='function')
def login(driver):
    driver.get('http://example.com/login')
    login_button = driver.find_element('id', 'login-btn')
    login_button.click()
    yield
    driver.quit()

A The fixture quits the driver after each test, causing stale element errors if reused.

B The fixture does not wait for page load before clicking, causing timing issues.

C The fixture uses function scope but should use module scope for driver reuse.

D The fixture yields before clicking the login button, so click never happens.

💡 Hint

Consider what happens to the driver after the test finishes.

Calling driver.quit() in the fixture teardown closes the browser. If tests reuse elements or driver, stale element errors occur.

❓ framework

expert

How to share a Selenium WebDriver instance across multiple test modules using conftest.py?

You want to create a shared Selenium WebDriver fixture in conftest.py that opens the browser once per test session and closes it after all tests finish. Which fixture definition achieves this?

A

import pytest

@pytest.fixture(scope='module')
def driver():
    from selenium import webdriver
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

B

import pytest

@pytest.fixture(scope='session')
def driver():
    from selenium import webdriver
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

C

import pytest

@pytest.fixture(scope='function')
def driver():
    from selenium import webdriver
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

D

import pytest

def driver():
    from selenium import webdriver
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

💡 Hint

Consider fixture scope to control browser lifetime.

Using scope='session' creates the driver once per test session, sharing it across modules. Other scopes create or quit the driver more often.