How does pytest discover tests SEO Brief & AI Prompts

pytest basics: assertions, test files, and discovery rules: pytest discovers tests by default by collecting functions named test_* and test classes named Test* from files that match the two filename patterns test_*.py and *_test.py, recursively under the current directory and its subdirectories. This behavior follows pytest's default collection rules and will import test modules to inspect for callables; test discovery will skip directories named with a leading dot or those excluded via pytest.ini patterns. The filename patterns are the single most important factor to ensure runnable tests in both local environments and CI. Test modules are imported with standard Python import semantics, so package layout and sys.path affect discovery.

Collection uses a mix of import-time introspection and AST-level analysis plus pytest's assert rewriting to produce rich failure diffs and local variable values, which distinguishes pytest from unittest and plain assert statements. Tools such as tox and CI runners invoke pytest's collector, which applies pytest naming conventions and discovery patterns from pytest.ini, pytest.conf, or pyproject.toml to include or ignore paths. The test collector looks for functions, methods, and classes, then creates nodes that are executed by the runner; fixtures declared in conftest.py provide dependency injection across collected tests. Command-line flags like -k for substring selection and -q for quieter output alter what the collector runs without changing file layout. Plugins such as pytest-xdist or coverage integrate at collection and runtime.

A frequent misconception is that plain Python assert yields the same output across runners; in reality pytest's assert rewriting transforms assert expressions at import time so failures include evaluated operands and inline diffs, unlike unittest's self.assertEqual style, which explains why raw assert formatting may look sparse outside pytest. Another common pitfall is incorrect naming: files like testsinstead.py or classes named TestMath without test_ prefixed functions will not be collected, breaking pytest test discovery. Misplacing conftest.py in the wrong package root can hide fixtures from subpackages in CI, causing inexplicable fixture lookup errors. Correct adherence to pytest test files naming and conftest.py fixtures placement prevents most discovery-related failures. Selection flags like -k can hide absent tests during collection and thus obscure true collection results.

Practical steps include naming test files using the test_*.py or *_test.py patterns, writing test functions named test_* or methods in classes named Test*, relying on pytest assertions so assert rewriting yields informative diffs, and placing shared fixtures in conftest.py at the repository root or package root so CI sees them. Running pytest with -q and using -k expressions helps narrow runs during development while preserving discovery rules for CI. The rest of this page provides a structured, step-by-step framework for writing pytest tests, arranging pytest test files, and configuring discovery rules for reliable local and CI execution.