Unit Testing Architecture

Establish co-located unit tests right beside the code they exercise using consistent naming suffixes to prevent orphaned suites. This keeps Go, TypeScript, and Python tests structured and easily discoverable within your UI, API, and sidecar directories.

Unit tests become brittle when target scenarios lack coherent patterns and proper isolation. Enforcing arrange-act-assert, per-test fixtures, centralized mock factories, and cleanup hooks ensures every test runs independently and remains reliable.

Structure mocks by establishing centralized mock factories, per-test fixtures, and cleanup hooks. Pairing this with dependency injection and interface boundaries ensures every test runs independently and relies on a stable, organized mock foundation.

Dependency injection introduces testable production code and clear interface boundaries. This structure makes your unit test architecture robust and provides a stable foundation for downstream testing skills to build upon.

Document unit test architecture by generating a UNIT_TEST_ARCHITECTURE.md audit report. This report records your test utilities, isolation routines, and centralized mock patterns so downstream skills and developers can rely on a stable structure.