Write unit tests

Unit tests catch bugs before they reach production, serve as documentation for expected behavior, and give developers confidence to refactor code without breaking functionality.

Quick Reference

• Test business logic, utilities, and edge cases
• Aim for 80%+ coverage on critical paths
• Use descriptive test names that explain behavior
• Mock external dependencies, not internal modules
• Run tests in CI to catch regressions early

Check

Check if this codebase has unit tests with good coverage for critical functionality.

Fix

Write unit tests for untested functions and components to improve code reliability.