Why test frameworks structure execution in Selenium Python

Introduction

Test frameworks organize how tests run to keep things simple and reliable. They help run many tests in order and handle setup and cleanup automatically.

When you want to run many tests without doing each one by hand.

When tests need to prepare something before running and clean up after.

When you want clear reports showing which tests passed or failed.

When tests depend on each other or must run in a certain order.

When you want to save time by running tests automatically.

Syntax

Selenium Python

import unittest

class TestExample(unittest.TestCase):
    def setUp(self):
        # runs before each test
        pass

    def test_something(self):
        # a test case
        pass

    def tearDown(self):
        # runs after each test
        pass

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

setUp prepares the test environment before each test.

tearDown cleans up after each test to avoid side effects.

Examples

Prepare the browser before each test starts.

Selenium Python

def setUp(self):
    self.driver = webdriver.Chrome()
    self.driver.get('https://example.com')

Close the browser after each test to free resources.

Selenium Python

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

Check if the page title is correct.

Selenium Python

def test_title(self):
    self.assertEqual(self.driver.title, 'Example Domain')

Sample Program

This test opens a browser, goes to example.com, checks the page title, then closes the browser. The framework runs setUp before the test and tearDown after.

Selenium Python

import unittest
from selenium import webdriver

class TestExample(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://example.com')

    def test_title(self):
        self.assertEqual(self.driver.title, 'Example Domain')

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

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

Important Notes

Test frameworks handle running tests in order and report results clearly.

Using setUp and tearDown avoids repeating code in each test.

Frameworks help keep tests independent and easy to maintain.

Summary

Test frameworks organize test running to make testing easier and reliable.

They provide setup and cleanup steps automatically for each test.

This structure helps run many tests and get clear results fast.

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