Pytest-cov Coverage — ELI5

Imagine cleaning your room at night with only a tiny phone light. You might tidy the center, but miss dust under the bed. Test coverage is a brighter flashlight: it shows which parts of your code your tests actually touched.

pytest runs your tests. pytest-cov adds a map that answers: “Which lines were visited?” A high number can feel good, but the real value is finding blind spots. If checkout logic never runs in tests, coverage highlights it before a customer finds the bug.

Coverage is not the same as quality. If a test only checks that a function runs, but never checks correct results, coverage can look great while bugs still exist. Good teams use coverage as a guide, then write stronger assertions.

A practical habit: when you fix a production bug, add a test first, run coverage, and confirm that bug path is now lit up. Over time, your risky paths become protected paths.

You can start with one command in CI and a small goal, like “no PR decreases coverage on changed files.” That keeps pressure focused on progress, not perfection.

The one thing to remember: coverage is a flashlight, not a trophy—use it to find what your tests are missing.