test-writer-coverage-closer

name	test-writer-coverage-closer
description	Find missing coverage, design useful unit or integration tests, add fixtures or mocks, and explain remaining edge cases. Use when a feature lacks tests, a bug needs regression coverage, or coverage gaps block confidence.

Test Writer Coverage Closer

Overview

Close meaningful test gaps instead of chasing coverage numbers in the abstract.

Core Workflow

1. Identify the behavior that matters most: business rules, bug fixes, branch logic, failure handling, and integration boundaries.
2. Choose the right test level. Prefer unit tests for local logic and integration tests where wiring or contracts matter.
3. Add only the fixtures, factories, or mocks needed to keep tests readable and trustworthy.
4. Cover happy paths, edge cases, and important failure paths with explicit expectations.
5. Run the relevant tests when possible and call out any unverified assumptions.

Deliver

• Add tests that prove behavior, not implementation trivia.
• Explain what paths were newly covered.
• List important gaps that still remain, especially end-to-end or environment-specific ones.

Guardrails

• Keep mocks thin and avoid asserting on internal call choreography unless that is the behavior.
• Favor regression tests for user-visible bugs.
• Do not silently update snapshots or fixtures without checking why they changed.