Why test frameworks structure execution in Selenium Python - Test Execution Impact

Test Overview

This test checks how a simple Selenium test framework structures the execution flow to open a browser, navigate to a page, find an element, click it, and verify the result. It verifies that the framework controls the order of actions and assertions to ensure reliable testing.

Test Code - Selenium with unittest

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import unittest

class TestFrameworkStructure(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.implicitly_wait(5)

    def test_button_click_changes_text(self):
        self.driver.get('https://example.com/button')
        button = WebDriverWait(self.driver, 10).until(
            EC.element_to_be_clickable((By.ID, 'change-text-btn'))
        )
        button.click()
        changed_text = WebDriverWait(self.driver, 10).until(
            EC.visibility_of_element_located((By.ID, 'text'))
        )
        self.assertEqual(changed_text.text, 'Text changed!')

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts and setUp method opens Chrome browser with implicit wait	Chrome browser window opens, ready for commands	—	PASS
2	Navigates to 'https://example.com/button'	Browser loads the page with a button having id 'change-text-btn' and a text element with id 'text'	—	PASS
3	Waits until the button with id 'change-text-btn' is clickable	Button is visible and enabled on the page	Button is clickable	PASS
4	Clicks the button	Button click triggers text change on the page	—	PASS
5	Waits until the text element with id 'text' is visible	Text element is visible on the page	Text element is visible	PASS
6	Checks that the text content equals 'Text changed!'	Text element shows 'Text changed!'	Assert text equals 'Text changed!'	PASS
7	tearDown method closes the browser	Browser window closes	—	PASS

Failure Scenario

Failing Condition: Button with id 'change-text-btn' is not found or not clickable

Execution Trace Quiz - 3 Questions

What does the test wait for before clicking the button?

A The text element to be visible

B The button to be clickable

C The page to fully load

D The browser to close

Key Result

Test frameworks structure execution to control the order of actions and checks, making tests reliable and easier to debug by waiting for elements and verifying expected results step-by-step.

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