Why CI integration enables continuous quality in PyTest - Test Execution Impact

Test Overview

This test checks that a simple function works correctly and runs automatically in a Continuous Integration (CI) environment. It verifies that CI integration helps catch errors early and keeps software quality high by running tests on every code change.

Test Code - pytest

PyTest

import 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

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts in CI environment triggered by code push	CI server initializes test environment with Python 3.12	-	PASS
2	pytest discovers test_add function	Test runner ready to execute test_add	-	PASS
3	pytest runs test_add and calls add(2, 3)	Function add returns 5	assert 5 == 5	PASS
4	pytest runs test_add and calls add(-1, 1)	Function add returns 0	assert 0 == 0	PASS
5	pytest runs test_add and calls add(0, 0)	Function add returns 0	assert 0 == 0	PASS
6	All assertions passed, pytest reports success	CI server receives test report with all tests passing	All test assertions passed	PASS

Failure Scenario

Failing Condition: If the add function returns wrong result, e.g., add(2, 3) returns 6

Execution Trace Quiz - 3 Questions

What triggers the test to run in a CI environment?

A Tests run only on developer's local machine

B Tests run only when manually started

C A code push or merge triggers the CI pipeline

D Tests run randomly without triggers

Key Result

Integrating tests into a CI pipeline ensures tests run automatically on every code change, catching bugs early and maintaining continuous software quality.