Why test frameworks structure execution in Selenium Python - Automation Benefits in Action

Verify login functionality with structured test execution

Preconditions (2)

Step 1: Open the login page URL

Step 2: Enter '[e-mail]' in the email input field with id 'email'

Step 3: Enter 'Password123' in the password input field with id 'password'

Step 4: Click the login button with id 'loginBtn'

Step 5: Wait for the dashboard page to load

Step 6: Verify the URL is 'https://example.com/dashboard'

Step 7: Verify the welcome message with id 'welcomeMsg' contains 'Welcome, user!'

✅ Expected Result: User is successfully logged in and redirected to the dashboard page with the welcome message displayed.

Automation Requirements - Selenium with Python unittest

Assertions Needed:

Assert current URL is 'https://example.com/dashboard'

Assert welcome message text contains 'Welcome, user!'

Best Practices:

Use unittest framework to structure test setup, execution, and teardown

Use explicit waits to wait for elements or page load

Use clear and maintainable locators (by ID)

Separate setup and cleanup code in setUp and tearDown methods

Automated Solution

Selenium Python

import unittest
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

class TestLogin(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.maximize_window()
        self.wait = WebDriverWait(self.driver, 10)

    def test_login_success(self):
        driver = self.driver
        driver.get('https://example.com/login')

        email_input = self.wait.until(EC.visibility_of_element_located((By.ID, 'email')))
        email_input.send_keys('[e-mail]')

        password_input = driver.find_element(By.ID, 'password')
        password_input.send_keys('Password123')

        login_button = driver.find_element(By.ID, 'loginBtn')
        login_button.click()

        # Wait for dashboard URL
        self.wait.until(EC.url_to_be('https://example.com/dashboard'))
        self.assertEqual(driver.current_url, 'https://example.com/dashboard')

        # Verify welcome message
        welcome_msg = self.wait.until(EC.visibility_of_element_located((By.ID, 'welcomeMsg')))
        self.assertIn('Welcome, user!', welcome_msg.text)

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

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

This test script uses the unittest framework to structure the test execution clearly. The setUp method opens the browser and prepares the wait object. The test method test_login_success performs the login steps exactly as described in the manual test case.

Explicit waits ensure the script waits for elements to appear or the URL to change before proceeding. This avoids timing issues.

Assertions check that the URL is correct and the welcome message is displayed, confirming successful login.

The tearDown method closes the browser after the test, keeping tests isolated and clean.

This structure helps keep tests organized, easy to read, and reliable, which is why test frameworks structure execution this way.

Common Mistakes - 3 Pitfalls

Not using explicit waits and relying on fixed sleep times

Mixing test logic and setup/cleanup code in one method

Using brittle locators like absolute XPaths

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials (valid and invalid) to verify login behavior.

Show Hint

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