Testing Standards

The 3-layer testing pyramid distributes tests as unit (95%), integration (85%), and E2E (critical paths only). Organize unit tests with 1:1 file mapping to production files, add integration tests for component interactions, and E2E tests for user workflows. This structure ensures fast feedback, realistic coverage, and maintainable test suites.

Create one test file per production file for unit tests, use shared fixtures for common test data and setup, and document test purposes in a reference.md. Organize fixtures by scope (function, module, session) and centralize reusable fixtures in conftest.py to reduce duplication and improve maintainability.

Set coverage targets aligned to test layers: 95% for unit tests, 85% for integration tests. Use coverage tools to measure and audit test suites against these benchmarks. Apply 1:1 file mapping and documented standards to ensure consistent coverage and identify untested code paths.

Write unit tests that are fast, isolated, and map 1:1 to production files. Use fixtures for setup, avoid external dependencies, and keep tests focused on single behaviors. Document test intent and maintain a reference guide to ensure tests remain reliable and maintainable over time.

Unit tests verify individual functions in isolation (95% of tests). Use integration tests to validate component interactions and data flows (85% coverage). Reserve E2E tests for critical user workflows and system boundaries. This pyramid approach balances speed, confidence, and maintenance cost.

Audit test organization against the 3-layer pyramid, verify 1:1 mapping for unit tests, and measure coverage against targets (95% unit, 85% integration). Document standards in reference.md and use automated tools to enforce consistent file structure, fixtures, and coverage thresholds.