Pytest Wrap

Problem

Python test workflows often involve more than running pytest. Developers may need to infer entry commands, test layout, configuration priority, and where to start when failures appear. If these details are scattered across pytest.ini, pyproject.toml, setup.cfg, or CI scripts, an ad hoc command can miss project conventions. Pytest Wrap addresses this context problem by framing pytest-related work as a skill entry point, reducing guesswork.

How It Works

• Core scope: provides a pytest-focused perspective for Python testing tasks and helps confirm test commands and environment.
• Key steps: locate test files and configuration first, then choose single tests, module-level runs, or failure-output analysis based on the request.
• Collaboration style: it encourages reading project configuration before executing test-related actions, instead of assuming every repository uses the same flags.

Boundaries and Notes

• The name and category indicate a dev-programming and Python focus, but it should not be assumed to include coverage, mocking, or parallel execution.
• If the repository already uses Makefile, Poetry, tox, or CI-defined test entry points, prefer those existing conventions.
• When specific command flags are not documented, do not interpret it as a particular plugin or framework replacement.