Pytest taste — ChatGPT prompt for pytest testing
Pytest taste is a ChatGPT prompt that sets conventions for Python tests written with pytest. It guides test structure, fixtures, assertions, and suite configuration.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Pytest taste does
Pytest taste lays out a testing style for Python packages: use plain assert, keep tests in a top-level tests/ directory, and put pytest settings in pyproject.toml. It favors small fixtures in the closest conftest.py and readable ids for @pytest.mark.parametrize cases.
The prompt recommends checking exception messages with pytest.raises(..., match=...), using tmp_path and monkeypatch, and replacing HTTP calls at the application boundary. Tests should not reach external services by default; integration tests run separately from the fast suite.
For async tests, it names pytest-asyncio and anyio in strict mode. It also suggests pytest-xdist for parallel runs and pytest-cov for coverage; these are recommendations, not required dependencies for the prompt.
What it helps with
- organize tests to mirror a Python package
- replace test loops with parametrized cases
- check exception messages as well as types
- keep tests from reaching external services
- separate integration tests from the fast suite
Example prompts for the agent
- Write pytest tests for this Python module using Pytest taste.
- Move the pytest settings into
pyproject.tomland organize the test folders. - Rewrite this test with fixtures and
@pytest.mark.parametrize.
How to install Pytest taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Pytest taste
How do I install Pytest taste in Claude Code?
Add the prompt file at .claude/commands/prompts.csv.md.
What does Pytest taste do?
It sets conventions for pytest suites, including test layout, fixtures, exception checks, and isolation from external services.
How does Pytest taste recommend configuring pytest?
Keep settings in pyproject.toml, enable --strict-markers and --strict-config, and treat warnings as errors while allowing known third-party warnings explicitly.
Source text
prompts.csv · CC0-1.0
# Pytest taste of a Python developer who wants fast, honest test suites - Use plain `assert` statements and let pytest's assertion rewriting explain failures instead of `unittest`-style assert methods. Confidence: 0.95 - Keep tests in a top-level `tests/` directory that mirrors the package layout, with the package installed in editable mode. Confidence: 0.85 - Configure pytest in `pyproject.toml` under `[tool.pytest.ini_options]` rather than a separate `pytest.ini` or `setup.cfg`. Confidence: 0.85 - Turn on `--strict-markers` and `--strict-config` so typos in markers or settings fail loudly. Confidence: 0.85 - Set `filterwarnings = ["error"]` and allowlist known third-party warnings explicitly, so deprecations are caught early. Confidence: 0.75 - Prefer small, composable fixtures over one giant fixture that builds the whole world. Confidence: 0.90 - Use the narrowest fixture scope that keeps tests fast; reach for `session` scope only for genuinely expensive, read-only resources. Confidence: 0.80 - Put shared fixtures in the nearest `conftest.py`, not one root conftest that every test imports implicitly. Confidence: 0.75 - Use `@pytest.mark.parametrize` with readable `ids` instead of loops inside a single test. Confidence: 0.90 - Use the built-in `tmp_path` and `monkeypatch` fixtures before writing custom temp-dir or env-var helpers. Confidence: 0.90 - Mock at the boundary (HTTP, clock, filesystem) and avoid patching internals of the code under test. Confidence: 0.85 - Use `respx`, `responses` or a fake server for HTTP instead of hand-rolled `MagicMock` chains. Confidence: 0.75 - Freeze time with `time-machine` or `freezegun` rather than sleeping or comparing against `datetime.now()`. Confidence: 0.80 - Assert on exceptions with `pytest.raises(..., match=...)` so the message is checked, not just the type. Confidence: 0.85 - Mark slow and integration tests with custom markers and run them in a separate CI job. Confidence: 0.80 - Run the suite in parallel with `pytest-xdist` once it takes more than a minute, and keep tests order-independent so that works. Confidence: 0.80 - Use `pytest-randomly` or random ordering to flush out hidden test coupling. Confidence: 0.65 - Measure coverage with `pytest-cov` and branch coverage on, but treat the number as a signal, not a target. Confidence: 0.75 - Use Hypothesis for parsers, serializers and pure functions where property-based tests find edge cases examples miss. Confidence: 0.70 - Never let tests hit real external services by default; block network access and opt in explicitly. Confidence: 0.80 - Use `pytest-asyncio` or `anyio` in strict mode for async code, never `asyncio.run` inside tests. Confidence: 0.75 - Keep each test focused on one behavior with an Arrange, Act, Assert shape and a name that reads like a sentence. Confidence: 0.85
© f · CC0-1.0 · f/prompts.chat