Test your pytest-cov knowledge with a free interactive quiz — 22 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What does `--cov-append` do?
Questions in this quiz
What does `--cov-append` do?
What is the basic command to run tests with coverage reporting via pytest-cov?
What does `--cov-fail-under=N` do?
What is the relationship between pytest-cov and coverage.py?
What does "line coverage" measure?
What is a common reason a team might `omit` a directory like `*/migrations/*` from coverage measurement?
Why is 100% coverage NOT the same thing as "the code is fully tested and bug-free"?
Why might a team specifically choose NOT to chase 100% coverage as a hard rule, even though pytest-cov makes tracking the exact percentage easy?
What is the effect of adding `# pragma: no cover` as a comment on a line or block?
How does pytest-cov handle coverage measurement when tests are run in parallel (e.g. via pytest-xdist)?
If a project's coverage percentage suddenly drops after a pull request, what is the most direct way to see exactly what caused it using pytest-cov's output?
What is the typical output of `pytest --cov=mypackage --cov-report=html` beyond the terminal summary?