home/business/testing-strategy

Testing Strategy

GPTClaudeGemini··▲ 368 copies·updated 2026-07-14

testing-strategy.prompt

# Lens: Testing Strategy

> Reusable analysis lens. Decide what tests to write, at what level, and what already exists.

## Purpose
Produce a concrete test plan: unit / integration / contract / E2E split, fixtures needed, manual-only scenarios, and what existing coverage already handles.

## Length budget
**≤30 lines.** List only the test files actually needed. Don't enumerate every test case — group as "happy / failure / boundary" bullets under each file.

## When to use
- Every story. Test planning before code prevents shallow / structure-only tests later.

## Inputs expected
- Assembled story context (especially ACs and edge-cases lens output).
- Discovered test conventions from project context (test folders, frameworks, coverage gates).

## Output template

when to use it

Community prompt sourced from the open-source GitHub repo shuchitajain/story-agent (MIT). A "Testing Strategy" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.