[Solved] Examine the following pytest fixture code for browser setup and teardown. What is the issue here?@pytest.fixture def browser(): driver = webdriver.Chrome() yield driver driver.quit() driver = None | Selenium Python

Selenium Python - Test Framework Integration (pytest)

Examine the following pytest fixture code for browser setup and teardown. What is the issue here?

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

AThe fixture is missing a return statement instead of yield.

BThe yield statement should be placed after driver.quit() to ensure proper setup.

Cdriver.quit() should be called before yield to close the browser before the test runs.

DSetting driver to None after quitting is unnecessary and has no effect on teardown.

Step-by-Step Solution

Solution:

Step 1: Analyze the fixture flow
The fixture creates a WebDriver instance, yields it for the test, then calls driver.quit() to close the browser.
Step 2: Check the line after driver.quit()
Setting driver = None after quitting the driver is redundant because the driver object is already closed and will be garbage collected.
Final Answer:
Setting driver to None after quitting is unnecessary and has no effect on teardown. -> Option D
Quick Check:
Yield must come before quit; setting driver to None is harmless but redundant. [OK]

Quick Trick: Yield before quit; no need to set driver to None after quitting [OK]

Common Mistakes:

Master "Test Framework Integration (pytest)" in Selenium Python

9 interactive learning modes - each teaches the same concept differently

More Selenium Python Quizzes

Examine the following pytest fixture code for browser setup and teardown. What is the issue here?