Fixtures for browser setup/teardown in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of pytest fixture with browser setup

What will be the output of the following pytest test when run?

Note: The fixture opens a browser, navigates to example.com, then closes the browser after the test.

Selenium Python

import pytest
from selenium import webdriver

@pytest.fixture
 def browser():
  driver = webdriver.Chrome()
  driver.get('https://example.com')
  yield driver
  driver.quit()

def test_title(browser):
  assert 'Example Domain' in browser.title
  print('Test Passed')

A Test Passed printed and test passes

B Test Passed printed but test fails with AssertionError

C No output printed, test passes silently

D Test fails with WebDriverException due to missing driver

💡 Hint

The fixture yields the driver after opening the page, so the test can access the page title.

The fixture sets up the browser and navigates to example.com. The test asserts the title contains 'Example Domain', which is true, so the assertion passes and 'Test Passed' is printed. The fixture then quits the browser after the test.

❓ assertion

intermediate

Correct assertion to verify browser is closed after test

Given a pytest fixture that opens and closes a browser, which assertion correctly verifies the browser is closed after the test?

Selenium Python

import pytest
from selenium import webdriver

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

def test_browser_closed(browser):
  pass  # Which assertion below is correct here?

A assert browser.current_url == ''

B assert browser.session_id is None

C assert browser.title == ''

D assert browser is None

💡 Hint

When the browser is closed, the session_id becomes None.

After driver.quit(), the session_id attribute becomes None indicating the browser session is closed. Other attributes like current_url or title raise exceptions or remain unchanged until accessed.

🔧 Debug

advanced

Identify the bug in fixture teardown

What is the bug in this pytest fixture for browser setup and teardown?

Selenium Python

import pytest
from selenium import webdriver

@pytest.fixture
 def browser():
  driver = webdriver.Chrome()
  driver.get('https://example.com')
  yield driver
  driver.close()  # Bug here

def test_example(browser):
  assert 'Example Domain' in browser.title

A driver.close() closes only the current window, not the browser session, causing resource leaks

B driver.close() raises an exception because it is called after yield

C driver.close() should be replaced with driver.quit() to avoid syntax error

D No bug, the fixture works correctly

💡 Hint

driver.close() and driver.quit() behave differently in Selenium.

driver.close() closes the current browser window but does not end the WebDriver session, which can leave the browser process running. driver.quit() properly ends the session and closes all windows.

❓ framework

advanced

Best practice for browser fixture scope in pytest

Which pytest fixture scope is best to use for browser setup/teardown to speed up multiple UI tests without side effects?

A scope='class' to open browser once per test class

B scope='function' to open and close browser for each test function

C scope='module' to open browser once per test module

D scope='session' to open browser once per test session

💡 Hint

Consider test isolation and speed trade-offs.

Using scope='module' opens the browser once per module, balancing speed and isolation. 'function' is slow, 'session' risks side effects across unrelated tests, 'class' is less common and depends on test organization.

🧠 Conceptual

expert

Why use yield in pytest fixtures for browser setup?

Why is the yield statement preferred over return in pytest fixtures that setup and teardown a browser?

A Yield returns the browser object faster than return

B Return cannot be used in fixtures, only yield is allowed

C Return causes the fixture to run multiple times, yield runs once

D Yield allows running teardown code after the test finishes, return does not

💡 Hint

Think about how pytest manages setup and teardown with fixtures.

Yield pauses the fixture to run the test, then resumes to run teardown code after the test. Return ends the fixture immediately, so no teardown code runs after the test.