python-package-testing

Place test files in a tests/ directory with a conftest.py for shared fixtures, write descriptive test functions using plain assert statements, and run them with the pytest command. Group related tests in classes and test one concept per function.

Run pytest --cov=your_package --cov-report=term-missing to see line-by-line coverage in the terminal, or use --cov-report=html for a browsable report. Aim for 80%+ overall coverage and 100% on critical business logic.

Use pytest.raises with a match pattern, for example with pytest.raises(ValueError, match="error message") around the failing call. For warnings, use pytest.warns with the expected warning class and message pattern.

Yes, run pytest --doctest-modules on your source directory to execute docstring examples as tests. Examples requiring unavailable credentials or external APIs should be documented but excluded from automated execution.

Retry backoff messages indicate an underlying design issue such as an agent calling a tool multiple times, excessive reasoning steps, or redundant API calls. Fix the root logic rather than suppressing the messages, and validate tool calls with thread inspection.