Unit Testing Architecture

What problem does it solve?

When target scenarios lack coherent unit testing patterns, tests become scattered, brittle, and hard to trust, hindering future development and making automated verification an afterthought instead of a foundation.

Core Features & Use Cases

• Test file co-location and naming standards keep Go, TypeScript, and Python unit tests right beside the code they exercise with consistent suffixes, preventing orphaned suites.
• Isolation and mock organization enforce arrange-act-assert, per-test fixtures, centralized mock factories, and cleanup hooks so every test runs independently.
• Testable production code plus documentation introduces dependency injection, interface boundaries, and a UNIT_TEST_ARCHITECTURE.md audit report so downstream skills can build on a stable structure.

Quick Start

Ask the unit testing architecture skill to audit the target scenario, co-locate the tests, and enforce the mock and DI patterns.