Why CI integration enables continuous quality in PyTest - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does CI integration improve software quality?

Continuous Integration (CI) tools run tests automatically when code changes are made. Which of the following best explains why this helps maintain continuous quality?

A CI delays testing until deployment to production to save time.

B CI replaces manual testing, so testers are no longer needed.

C CI runs tests only after all features are complete, ensuring final quality.

D CI runs tests frequently, catching bugs early and preventing broken code from merging.

💡 Hint

Think about how often tests run and when bugs are found.

CI runs tests automatically on every code change, so bugs are found early. This prevents broken code from being merged and keeps quality high continuously.

❓ Predict Output

intermediate

What is the test result when CI runs this pytest test?

Given the following pytest test code, what will be the test result when run in a CI pipeline?

PyTest

def add(a, b):
    return a + b

def test_add():
    assert add(2, 3) == 5
    assert add(-1, 1) == 0
    assert add(0, 0) == 0

A All tests pass successfully.

B One test fails due to incorrect assertion.

C SyntaxError occurs because of missing colon.

D TypeError occurs because add function is missing parameters.

💡 Hint

Check if the function and assertions are logically correct.

The add function correctly sums two numbers. All assertions match expected results, so all tests pass.

❓ assertion

advanced

Which assertion best verifies a web page title in CI tests?

In a CI test for a web app, you want to check that the page title is exactly 'Welcome Page'. Which pytest assertion is best?

PyTest

page_title = get_page_title()  # returns the current page title string

A assert 'Welcome' in page_title

B assert page_title == 'Welcome Page'

C assert page_title.startswith('Welcome')

D assert page_title != ''

💡 Hint

Think about exact match vs partial or presence checks.

To verify the title exactly matches 'Welcome Page', use equality assertion. Other options only check partial or non-empty strings.

🔧 Debug

advanced

Why does this pytest test fail in CI?

Review the pytest test below. It passes locally but fails in CI with a KeyError. Why?

PyTest

def get_user(data, key):
    return data[key]

def test_get_user():
    user = {'name': 'Alice'}
    assert get_user(user, 'name') == 'Alice'
    assert get_user(user, 'age') == 30

A KeyError occurs because 'age' key is missing in the dictionary.

B SyntaxError due to missing colon in function definition.

C AssertionError because 'age' value is 25, not 30.

D TypeError occurs because get_user expects a list, not dict.

💡 Hint

Check dictionary keys and what happens when a missing key is accessed.

Accessing a missing key in a dictionary raises KeyError. The test expects 'age' key which is not present, causing failure in CI.

❓ framework

expert

Which pytest fixture usage best supports CI continuous testing?

In a CI environment, you want to run tests that need a temporary database setup and teardown for each test. Which pytest fixture usage is best?

A

@pytest.fixture(scope='class')
def temp_db():
    setup_db()
    yield
    teardown_db()

B

@pytest.fixture(scope='session')
def temp_db():
    setup_db()
    yield
    teardown_db()

C

@pytest.fixture(scope='function')
def temp_db():
    setup_db()
    yield
    teardown_db()

D

@pytest.fixture(scope='module')
def temp_db():
    setup_db()
    yield
    teardown_db()

💡 Hint

Consider how often the database should reset for test isolation in CI.

Using function scope runs setup and teardown for each test, ensuring clean state and preventing test interference, which is ideal for CI.