Menü
What to test at unit vs integration vs e2e.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | testing-strategy |
| description | What to test at unit vs integration vs e2e. |
| Layer | Tests |
|---|---|
| Pure logic | Unit, many, fast |
| DB/API adapters | Integration, fewer |
| Critical journeys | E2E, handful |
Pyramid: many unit, some integration, few e2e. Prefer fakes over mocks for clarity.
Write Architecture Decision Records when choosing between real alternatives.
When the agent loop is stuck: capture, shrink, recover.
REST/JSON API consistency: resources, errors, pagination.
Structured review output with severities and explicit approval gate.
Systematic debug: reproduce, isolate, fix, prevent.
Consistent error strategy across layers.
