Testing Writing Guidelines

Write focused unit tests by identifying critical paths and drafting behavior-focused assertions that validate main user workflows. Use descriptive test names and mock external dependencies to ensure rapid, deterministic execution without over-testing edge cases.

Mock external dependencies for integration testing by stubbing out external services and focusing assertions on primary functionality. This approach ensures fast execution and deterministic tests while validating critical paths without relying on slow, external systems.

Unit tests become flaky when they rely on external dependencies or undefined states. Make tests deterministic by mocking external systems, applying descriptive test names, and deferring edge cases to focus only on core user workflows and critical paths.

Defer edge cases during test strategy planning when prioritizing rapid feedback and fast execution. Focus initial unit and integration tests on core user workflows and critical paths, ensuring primary functionality is validated before exploring secondary scenarios.

Descriptive test names are required for behavior-focused assertions to clearly communicate the core user workflow being validated. This practice enforces clear test naming conventions and ensures rapid execution by focusing on primary functionality.