arogyareddy Test
Use this when asked to add tests, improve coverage, validate a bug fix, or design a test strategy.
Workflow
- Understand the behavior contract.
- Identify unit, integration, and end-to-end boundaries.
- Add high-signal tests first.
- Cover happy path, edge cases, invalid input, error handling, concurrency/async behavior, and regression scenarios.
- 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