test-guidelines

Unit tests should minimize mocks by testing real dependencies when possible. Focus on testing behavior rather than implementation details, use dependency injection for flexibility, and reserve mocks for external services or hard-to-control dependencies. This approach improves test reliability and maintainability.

Review tests using a structured checklist: verify independence between tests, check for over-mocking, ensure the AAA pattern (Arrange-Act-Assert), validate naming clarity, and confirm tests aren't bypassing the code under test. This identifies maintainability problems and hidden bugs.

Failing tests require systematic diagnosis: isolate the failure, verify test independence, check mock behavior, review assertions, and trace the actual code path. Distinguish between implementation bugs and test-design flaws to fix the root cause efficiently.

Follow the AAA pattern (Arrange-Act-Assert), write independent tests that don't depend on execution order, use clear naming conventions that describe intent, apply fixture and factory patterns for setup, and plan test strategy before writing. This ensures comprehensive coverage and maintainability.

Refactor to dependency injection when tests rely on excessive mocks or tight coupling to implementation. DI-based refactoring enables injecting real or stub dependencies, improves test clarity, reduces brittleness, and makes tests easier to maintain as code evolves.

Yes, test guidelines apply uniformly across all scenarios: creating new tests for features, reviewing and improving existing test suites, and diagnosing failed tests. Consistent workflows ensure code reliability, best-practice adherence, and efficient debugging regardless of context.