pytest
tool judged 0% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2024-W22 | 1 | 1 |
| 2024-W29 | 1 | 1 |
| 2026-W31 | 1 | 1 |
| 2026-W37 | 1 | 1 |
| 2026-W40 | 8 | 4 |
| 2026-W41 | 3 | 2 |
In their words
Keep rules short and testable Rules that work across tools are concrete: "Run pytest -q before declaring a task done." "Never edit files under migrations/ that are already committed." "Do not add a dependency without saying why in the PR description." Vague rules ("write clean code") get ignored by every tool.
Level 1: Unit Tests for Deterministic Parts # test_prompt_templates.py import pytest from myapp.prompts import format_rag_prompt , format_agent_prompt def test_rag_prompt_includes_context (): context = " The capital of France is Paris.
""" Model-Specific Tips GPT-4 / Claude Excellent at following complex instructions Handles long context well Good at structured output (JSON, YAML) Prefers explicit constraints Llama / Mistral (Open Weights) Benefits from more examples Needs clearer step-by-step Sometimes ignores negative constraints ("don't do X") Better with XML tags than markdown Small Models (7B and below) Few-shot critical Ke
Field What it holds Reject the skip when test_id One pytest node id Collection returns zero tests or more than one fixture_path Path of the snapshotted fixture file The path is missing on disk fixture_sha256 SHA-256 of those exact bytes The digest moved between the two runs disagreement Two run objects with opposite passed flags Both runs passed, or both failed oracle_path Property file path The p
Step 3: tests that actually catch bugs # tests/test_llm.py import pytest from llm import summarize from tests.fakes import FakeClient , completion def test_sends_expected_request (): fake = FakeClient ( completion ( " Short summary.
flowchart TD Start["🚨 Input: Legacy Visual ETL Node Graph"] --> T1["Task 01: Left Join & Imputation<br/>• Coerce nulls<br/>• Calculate is_vip flag"] Start --> T2["Task 02: Regex Extraction<br/>• Parse key-value logs<br/>• Retain corrupted rows"] Start --> T3["Task 03: Cumulative Windows<br/>• Running total cumsum()<br/>• Intra-department rank"] Start --> T4["Task 04: Matrix Reshaping<br/>• Melt wi
The workflow: Developer marks a test with @pytest.mark.llm_fuzz(budget_usd=5, params=["user_input"]) or the vitest equivalent Agent reads the test file and the code under test Agent generates adversarial inputs targeting the specified parameters CI runs the normal test suite with the generated inputs Only failing tests get reported The agent does not run the tests itself.
As a permissions config: { "permissions": { "allow": ["Read","Edit","Write","Grep","Glob", "Bash(git add:*)","Bash(git commit:*)", "Bash(npm test:*)","Bash(npm run:*)","Bash(npm ci:*)","Bash(pytest:*)"], "ask": ["Bash(git push:*)","Bash(npm publish:*)","Bash(aws:*)","Bash(terraform apply:*)","Bash(kubectl apply:*)"], "deny": ["Bash(git push --force:*)","Bash(git push -f:*)","Bash(*--no-verify*)"]