Bird
Raised Fist0
PyTesttesting~10 mins

Single responsibility per test in PyTest - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define a test that checks if the sum of two numbers is correct.

PyTest
def test_sum():
    result = 2 + 3
    assert result == [1]
Drag options to blanks, or click blank then click option'
A7
B5
C6
D4
Attempts:
3 left
💡 Hint
Common Mistakes
Using a wrong expected value in the assertion.
Forgetting to use assert keyword.
2fill in blank
medium

Complete the code to test if a list contains a specific element.

PyTest
def test_contains_element():
    fruits = ['apple', 'banana', 'cherry']
    assert 'banana' [1] fruits
Drag options to blanks, or click blank then click option'
Ain
Bnot in
C==
D!=
Attempts:
3 left
💡 Hint
Common Mistakes
Using '==' instead of 'in' for membership check.
Using 'not in' which checks the opposite.
3fill in blank
hard

Fix the error in the test function that checks if a string is uppercase.

PyTest
def test_is_uppercase():
    text = 'HELLO'
    assert text.[1]()
Drag options to blanks, or click blank then click option'
Aisupper
Bistitle
Cislower
Disalpha
Attempts:
3 left
💡 Hint
Common Mistakes
Using islower() which checks for lowercase letters.
Using istitle() which checks for title case.
4fill in blank
hard

Complete the code to create a test that checks if a list is sorted in ascending order.

PyTest
def test_sorted_list():
    numbers = [1, 2, 3, 4, 5]
    assert numbers == sorted(numbers)

    assert numbers[1] sorted(numbers)
Drag options to blanks, or click blank then click option'
B!=
C==
D[::-1]
Attempts:
3 left
💡 Hint
Common Mistakes
Adding unnecessary slicing inside sorted().
Using '!=' instead of '==' in the second assertion.
5fill in blank
hard

Fill both blanks to write a test that checks if a dictionary comprehension creates correct squares for numbers greater than 2.

PyTest
def test_squares_dict():
    numbers = [1, 2, 3, 4]
    squares = {n:: n[1] for n in numbers if n [2] 2}
    assert squares == {3: 9, 4: 16}
Drag options to blanks, or click blank then click option'
A**2
B>
C:
D*2
Attempts:
3 left
💡 Hint
Common Mistakes
Using '*' instead of '**' for squaring.
Using '<' instead of '>' in the condition.
Using ':' incorrectly in dictionary comprehension.

Practice

(1/5)
1. What is the main reason to write a test with a single responsibility in pytest?
easy
A. To run all tests faster at once
B. To make the test easier to understand and fix when it fails
C. To combine many checks in one test for efficiency
D. To avoid writing multiple test functions

Solution

  1. Step 1: Understand test clarity

    Tests with one responsibility focus on one behavior, making it clear what failed.
  2. Step 2: Benefits of single responsibility

    This clarity helps developers quickly find and fix issues without confusion.
  3. Final Answer:

    To make the test easier to understand and fix when it fails -> Option B
  4. Quick Check:

    Single responsibility = clarity and easier fixes [OK]
Hint: One test, one check, easy to read and fix [OK]
Common Mistakes:
  • Trying to test many things in one test
  • Ignoring test readability
  • Using unclear test names
2. Which of the following pytest test function names best follows the single responsibility principle?
easy
A. test_user_login_and_profile_update
B. test_all_user_functions
C. test_user_login_with_valid_credentials
D. test_user_actions

Solution

  1. Step 1: Analyze test names for specificity

    Names should describe one clear behavior or feature being tested.
  2. Step 2: Compare options

    test_user_login_with_valid_credentials clearly states it tests login with valid credentials only, so it has a single responsibility.
  3. Final Answer:

    test_user_login_with_valid_credentials -> Option C
  4. Quick Check:

    Clear, specific test name = single responsibility [OK]
Hint: Pick the test name that describes one clear action [OK]
Common Mistakes:
  • Using vague or combined test names
  • Testing multiple features in one test
  • Ignoring descriptive naming
3. Given this pytest code, what will be the test result?
def test_example():
    x = 5
    assert x == 5
    assert x > 0
medium
A. Test passes because both assertions are true
B. Test fails because multiple assertions are not allowed
C. Test fails because x is not defined
D. Test passes but only the first assertion is checked

Solution

  1. Step 1: Check variable and assertions

    Variable x is set to 5, which satisfies both assertions: x == 5 and x > 0.
  2. Step 2: Understand pytest assertion behavior

    Pytest allows multiple assertions; all are checked unless one fails first. Here both pass.
  3. Final Answer:

    Test passes because both assertions are true -> Option A
  4. Quick Check:

    All assertions true = test passes [OK]
Hint: Check each assertion truth; all must pass for test pass [OK]
Common Mistakes:
  • Thinking multiple assertions cause failure
  • Assuming only first assertion runs
  • Confusing variable scope
4. Identify the problem in this pytest test function that violates single responsibility:
def test_user():
    assert login('user') == True
    assert update_profile('user', 'new info') == True
medium
A. The test has syntax errors
B. The test uses invalid function calls
C. The test misses setup code
D. The test checks two different features in one function

Solution

  1. Step 1: Review test actions

    The test checks login and profile update in the same function, two separate features.
  2. Step 2: Understand single responsibility principle

    Each test should check only one behavior to keep tests clear and focused.
  3. Final Answer:

    The test checks two different features in one function -> Option D
  4. Quick Check:

    Multiple features in one test = violation [OK]
Hint: One test, one feature; multiple features break single responsibility [OK]
Common Mistakes:
  • Ignoring multiple assertions as multiple responsibilities
  • Assuming syntax errors cause failure here
  • Confusing setup with test logic
5. You have a test that checks user registration, login, and logout all in one function. How should you refactor it to follow single responsibility in pytest?
hard
A. Split the test into three separate tests: one for registration, one for login, and one for logout
B. Keep all checks in one test but add comments to separate them
C. Remove login and logout checks and test only registration
D. Combine registration and login in one test, logout in another

Solution

  1. Step 1: Identify responsibilities in the test

    The test currently checks three different user actions: registration, login, and logout.
  2. Step 2: Apply single responsibility principle

    Each test should focus on one action to improve clarity and maintainability.
  3. Step 3: Refactor approach

    Splitting into three tests ensures each test checks only one feature clearly.
  4. Final Answer:

    Split the test into three separate tests: one for registration, one for login, and one for logout -> Option A
  5. Quick Check:

    One test per feature = better clarity and easier fixes [OK]
Hint: Split combined tests into single-feature tests [OK]
Common Mistakes:
  • Keeping multiple features in one test with comments
  • Removing features instead of splitting
  • Partially splitting tests inconsistently