Testing Unit

Overview

Use this skill to validate small-scope logic quickly and deterministically with strong failure localization.

Scope Boundaries

• Use when correctness can be validated within isolated units.
• Typical requests:
  • Harden branch and edge-case logic with fast deterministic tests.
  • Verify exception paths and guard-rail behavior.
  • Isolate dependencies to pinpoint failure causes.
• Do not use when:
  • Cross-service compatibility is the core risk (testing-contract/testing-integration).
  • Full UI journey behavior is needed (testing-e2e/playwright).

Inputs

• Unit boundaries and behavior expectations
• Mock/stub strategy and dependency seams
• Runtime constraints for fast feedback loops