Why test frameworks structure execution in Selenium Python - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do test frameworks run tests in a structured order?

Test frameworks often run tests in a specific order or structure. Why is this important?

A To allow tests to share variables globally without resetting

B To ensure tests run independently and results are reliable

C To make tests run faster by skipping some tests randomly

D To make tests dependent on each other for better coverage

💡 Hint

Think about why test results should not be affected by other tests.

Running tests independently ensures that one test's result does not affect another. This makes test results reliable and easier to debug.

❓ Predict Output

intermediate

What is the output of this Selenium test execution order code?

Consider this simplified Selenium Python test code using unittest framework. What will be the printed order of test execution?

Selenium Python

import unittest

class SampleTest(unittest.TestCase):
    @classmethod
    def setUpClass(cls):
        print('SetupClass')

    def setUp(self):
        print('Setup')

    def test_one(self):
        print('Test One')

    def test_two(self):
        print('Test Two')

    def tearDown(self):
        print('TearDown')

    @classmethod
    def tearDownClass(cls):
        print('TearDownClass')

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

A

SetupClass
Setup
Test One
TearDown
Setup
Test Two
TearDown
TearDownClass

B

Setup
Test One
TearDown
Setup
Test Two
TearDown
SetupClass
TearDownClass

C

SetupClass
Test One
Test Two
TearDownClass

D

Setup
Test One
Setup
Test Two
TearDown
TearDownClass

💡 Hint

Remember the order of setUpClass, setUp, test methods, tearDown, and tearDownClass in unittest.

setUpClass runs once before all tests, setUp runs before each test, tearDown after each test, and tearDownClass once after all tests.

❓ assertion

advanced

Which assertion correctly verifies a page title in Selenium Python?

You want to check if the page title is exactly 'Welcome Page'. Which assertion is correct?

Selenium Python

from selenium import webdriver

browser = webdriver.Chrome()
browser.get('http://example.com')
page_title = browser.title

A assert 'Welcome' in page_title

B assert page_title > 'Welcome Page'

C assert page_title != 'Welcome Page'

D assert page_title == 'Welcome Page'

💡 Hint

Check for exact match of the title string.

Using '==' checks that the page title exactly matches 'Welcome Page'. Other options check partial match, inequality, or invalid comparison.

🔧 Debug

advanced

Why does this Selenium test fail to find the element?

Look at this Selenium Python code snippet. Why does it raise a NoSuchElementException?

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By

browser = webdriver.Chrome()
browser.get('http://example.com')
element = browser.find_element(By.ID, 'submit-btn')
print(element.text)

A The By.ID locator is deprecated and causes error

B The browser variable is not initialized correctly

C The element with ID 'submit-btn' does not exist on the page

D The print statement is incorrect syntax

💡 Hint

Check if the element ID matches any element on the loaded page.

NoSuchElementException means Selenium could not find an element with the given locator. Usually the element is missing or the locator is wrong.

❓ framework

expert

What is the main reason test frameworks isolate test cases during execution?

Test frameworks isolate each test case execution environment. What is the main reason for this isolation?

A To prevent side effects from one test affecting others and ensure consistent results

B To speed up test execution by running tests in parallel without waiting

C To allow tests to share global variables for easier data access

D To reduce the amount of code needed to write tests

💡 Hint

Think about test reliability and debugging ease.

Isolation prevents one test's changes from impacting others, making results reliable and debugging simpler.

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