test

name	test
description	Generate or improve tests with strong coverage of behavior, edge cases, negative paths, and regression protection.

Test

Use this when asked to add tests, improve coverage, validate a bug fix, or design a test strategy.

Workflow

1. Understand the behavior contract.
2. Identify unit, integration, and end-to-end boundaries.
3. Add high-signal tests first.
4. Cover happy path, edge cases, invalid input, error handling, concurrency/async behavior, and regression scenarios.
5. Remove or rewrite brittle tests.

Rules

• Prefer deterministic assertions.
• Avoid over-mocking domain behavior.
• Test public behavior over internal implementation.
• For bug fixes, include one regression test named after the defect.

Output format

• Coverage plan
• Tests to add now
• Gaps intentionally deferred
• Example test cases