{project}-testing

Standardize test organization by placing test files in tests/ and reusable sample data in tests/fixtures. This structure supports unit, integration, and E2E testing workflows while maintaining clear naming conventions for repeatable quality checks.

Standard naming conventions categorize test files by type—unit, integration, and E2E—within the tests/ directory. This structured organization ensures consistent identification and repeatable quality checks across the project's testing workflows.

Set up reusable fixtures by placing sample data in tests/fixtures to accelerate test development. This provides predefined sample data for consistent, repeatable quality checks across unit, integration, and end-to-end testing workflows.

No specific testing framework is required, as the patterns provide generic organizational templates and fixtures. These guidelines apply to typical software projects, ensuring structured descriptions and clear guidance for CI integration without framework dependencies.

Integrate test patterns into CI by applying the CI-ready patterns and running your pipeline to verify coverage and stability. The standardized structure ensures tests are automatically discovered and executed during continuous integration workflows.

The best way to structure E2E testing is using predefined organizational templates within the tests/ directory. This standardizes end-to-end workflows alongside unit and integration tests, ensuring repeatable quality checks and clear CI integration.