# Pytest Documentation Notes

!!! info "Primary sources"
    - [Good integration practices](https://docs.pytest.org/en/stable/explanation/goodpractices.html)
    - [Fixture how-to](https://docs.pytest.org/en/stable/how-to/fixtures.html)
    - [Marker examples](https://docs.pytest.org/en/stable/example/markers.html)
    - [Configuration reference](https://docs.pytest.org/en/stable/reference/customize.html)
    - [Flaky tests](https://docs.pytest.org/en/stable/explanation/flaky.html)

## Practical Guidance For This Skill
- Use src-aligned test layout and keep test discovery conventional.
- Keep fixtures small, composable, and explicit; use `yield` for teardown.
- Register custom markers and keep strict marker validation on.
- Separate quick unit runs from slower integration/external runs.
- Minimize flakiness by controlling shared state and avoiding hidden dependencies.
- Use `--collect-only` and marker-filtered runs to validate scaffold quality early.

## Commands Worth Remembering
- `uv run pytest --collect-only -q`
- `uv run pytest -m unit -q`
- `uv run pytest -m "not external" -q`
- `uv run pytest -q`