Skip to content
pytest-best-practices logo

pytest-best-practices

Expert guidance for writing high-quality pytest tests. Use when writing tests, setting up fixtures, parametrizing, mocking, or reviewing test code.

NeverSight/skills_feed0installs214stars

SKILL.md

Full skill instructions

<objective> Provide pytest best practices and patterns for writing maintainable, efficient tests. </​objective>

<essential_principles>

Test Independence

  • Each test must run in isolation - no shared state between tests
  • Use fixtures for setup/​teardown, never class-level mutable state
  • Tests should pass regardless of execution order

Naming Conventions

  • Files: test_*.py or *_test.py
  • Functions: test_<description>()
  • Classes: Test<ClassName>
  • Fixtures: descriptive lowercase_with_underscores

Directory Structure

tests/
├── conftest.py          # Shared fixtures
├── unit/
│   └── test_module.py
├── integration/
│   └── test_api.py
└── fixtures/            # Test data files

Core Testing Rules

  • Use plain assert statements (pytest provides detailed failure messages)
  • One logical assertion per test when practical
  • Test edge cases: empty inputs, boundaries, invalid data, errors
  • Keep tests focused and readable

</​essential_principles>

<quick_reference>

PatternUse Case
@pytest.fixtureSetup/​teardown, dependency injection
@pytest.mark.parametrizeRun test with multiple inputs
@pytest.mark.skipSkip test temporarily
@pytest.mark.xfailExpected failure (known bug)
pytest.raises(Exception)Test exception raising
pytest.approx(value)Float comparison
mocker.patch()Mock dependencies
conftest.pyShare fixtures across modules

Common Commands

pytest -v                    # Verbose
pytest -x                    # Stop on first failure
pytest --lf                  # Run last failed
pytest -k "pattern"          # Match test names
pytest -m "marker"           # Run marked tests
pytest --cov=src             # Coverage report

</​quick_reference>

<routing>

Based on what you're doing, read the relevant reference:

TaskReference
Setting up fixtures, scopes, factoriesreferences/​fixtures.md
Parametrizing tests, multiple inputsreferences/​parametrization.md
Mocking, patching, faking dependenciesreferences/​mocking.md
Markers, exceptions, assertions, asyncreferences/​patterns.md

</​routing>

<dependencies> ```bash pip install pytest pytest-asyncio pytest-mock pytest-cov pytest-xdist ``` </​dependencies>