Why CI integration enables continuous quality in PyTest - Automation Benefits in Action

Verify that CI integration runs tests automatically on code push

Preconditions (3)

Step 1: Push a commit with a small code change to the main branch

Step 2: Observe the CI service starting a test run automatically

Step 3: Wait for the test run to complete

Step 4: Check the test results in the CI dashboard

✅ Expected Result: The CI service automatically runs the pytest tests on the pushed commit and reports all tests passing without manual intervention

Automation Requirements - pytest

Assertions Needed:

Verify that pytest test suite runs without failures

Verify that test results are reported (simulated by pytest output)

Best Practices:

Use pytest fixtures for setup and teardown

Write clear and independent test functions

Use assert statements for validation

Keep tests fast and isolated

Automated Solution

PyTest

import pytest

# Sample function to test
def add(a, b):
    return a + b

# Test case to verify add function

def test_add_positive_numbers():
    assert add(2, 3) == 5

def test_add_negative_numbers():
    assert add(-1, -1) == -2

def test_add_zero():
    assert add(0, 0) == 0

# To run these tests, push this code to your Git repo and observe CI running pytest automatically

if __name__ == "__main__":
    pytest.main(["-v"])

This script defines a simple add function and three pytest test functions to check it with positive numbers, negative numbers, and zero.

Each test uses assert to verify the expected output.

When this code is pushed to a Git repository configured with CI (like GitHub Actions), the CI system will automatically run pytest and report the results.

This automation ensures continuous quality by running tests on every code change without manual effort.

Common Mistakes - 4 Pitfalls

Not using assert statements in pytest tests

Writing tests that depend on each other

{'mistake': 'Not configuring CI to run pytest on push', 'why_bad': "If CI is not set up properly, tests won't run automatically, losing continuous quality benefits.", 'correct_approach': 'Configure CI workflows to trigger pytest on every push or pull request.'}

Using print statements instead of asserts for validation

Bonus Challenge

Now add data-driven testing with 3 different input pairs for the add function

Show Hint

Practice

1. What is the main benefit of integrating pytest with Continuous Integration (CI) systems?

easy

A. CI integration slows down the development process

B. Tests run only when manually triggered by developers

C. Tests run automatically on every code change to catch bugs early

D. CI integration replaces the need for writing tests

Solution

1. Step 1: Understand CI integration purpose

   CI systems run tests automatically whenever code changes are pushed.

2. Step 2: Identify the benefit of automatic testing

   This automatic testing helps catch bugs early and maintain software quality continuously.

3. Final Answer:

   Tests run automatically on every code change to catch bugs early -> Option C

4. Quick Check:

   CI runs tests automatically = A [OK]

Hint: CI runs tests on every change to catch bugs early [OK]

Common Mistakes:

• Thinking tests run only manually
• Believing CI slows development
• Assuming CI replaces writing tests

2. Which pytest command is commonly used in a CI pipeline to run all tests?

easy

A. pytest --run-all

B. pytest

C. pytest --ci-mode

D. pytest --skip

Solution

1. Step 1: Recall pytest basic command

   The basic command to run all tests is simply pytest.

2. Step 2: Check other options for validity

   Options like --run-all, --ci-mode, and --skip are not standard pytest commands.

3. Final Answer:

   pytest -> Option B

4. Quick Check:

   Run all tests = pytest [OK]

Hint: Use plain 'pytest' to run all tests in CI [OK]

Common Mistakes:

• Adding non-existent flags
• Using commands that skip tests
• Confusing pytest options with other tools

3. Given this pytest output in a CI pipeline:

============================= test session starts =============================
collected 3 items

test_sample.py ..F                                                      [100%]

================================== FAILURES ===================================
____________________________ test_divide_by_zero _____________________________

    def test_divide_by_zero():
>       assert 1 / 0
E       ZeroDivisionError: division by zero

What does this output tell you about the test results?

medium

A. All tests passed successfully

B. Tests did not run because of a syntax error

C. Tests were skipped

D. One test failed due to a division by zero error

Solution

1. Step 1: Analyze the test summary

   The output shows 3 tests collected, with two dots (.) meaning passed tests and one F meaning a failure.

2. Step 2: Identify failure cause

   The failure is due to a ZeroDivisionError in test_divide_by_zero.

3. Final Answer:

   One test failed due to a division by zero error -> Option D

4. Quick Check:

   F indicates one test failed due to ZeroDivisionError = C [OK]

Hint: F means failure; check error message for cause [OK]

Common Mistakes:

• Assuming all tests passed
• Confusing failure with skipped tests
• Ignoring error details

4. You added pytest tests to your project and integrated them with CI. However, the CI pipeline always shows zero tests collected. What is the most likely cause?

medium

A. Test files or functions are not named correctly (e.g., missing 'test_' prefix)

B. The CI server is offline

C. pytest is not installed on the CI server

D. Tests contain assertion errors

Solution

1. Step 1: Understand pytest test discovery rules

   pytest only collects tests from files and functions named starting with test_.

2. Step 2: Identify why zero tests are collected

   If no tests are found, likely the naming conventions are not followed, so pytest skips them.

3. Final Answer:

   Test files or functions are not named correctly (e.g., missing 'test_' prefix) -> Option A

4. Quick Check:

   pytest needs 'test_' prefix to find tests [OK]

Hint: Name test files/functions starting with 'test_' [OK]

Common Mistakes:

• Assuming CI server offline causes zero tests
• Ignoring pytest naming conventions
• Thinking assertion errors prevent test collection

5. In a CI pipeline using pytest, you want to ensure that tests run only if code formatting passes with black --check. Which approach best integrates this to maintain continuous quality?

hard

A. Run black --check first; if it fails, stop the pipeline; else run pytest tests

B. Run pytest tests first; then run black --check regardless of test results

C. Run both black --check and pytest tests in parallel without stopping

D. Skip black --check and only run pytest tests

Solution

1. Step 1: Understand quality gate concept in CI

   Code formatting checks should block further testing if they fail to maintain quality.

2. Step 2: Determine correct pipeline order

   Run black --check first; if it fails, stop pipeline to fix formatting before running tests.

3. Final Answer:

   Run black --check first; if it fails, stop the pipeline; else run pytest tests -> Option A

4. Quick Check:

   Fail fast on formatting, then test = A [OK]

Hint: Fail formatting check before tests to keep quality [OK]

Common Mistakes:

• Running tests before fixing formatting
• Ignoring formatting failures
• Running checks in parallel without order