testing-guidelines

Prefer integration tests over isolated unit tests to validate user entry points and public interfaces. Use real-world fixtures for data setup and ensure test isolation to maintain robust code quality and prevent cross-test dependencies.

To write regression tests, add a specific test validating the fixed bug alongside your existing test suite. This ensures the exact user entry point is validated and prevents the same functionality from breaking in future code changes.

Mock external services whenever a test interacts with dependencies outside your codebase to ensure test isolation. This testing principle guarantees reliable validation of public interfaces without relying on unpredictable external network responses.

Organize test files by following clear technical standards for structure and isolation. This standardized methodology ensures your testing suite remains maintainable, validates pure functions correctly, and reliably covers user entry points before manual QA.