testing-plan

Generate a manual QA test plan by translating branch context and diffs into concrete route-based manual steps. The output is a human-executable markdown file with required sections, actors, actions, and expected results for browser verification.

Human-executable route testing is end-to-end browser verification across UI surfaces, server endpoints, auth, and schema changes. It provides testers with concrete manual steps and expected results tied directly to the current branch changes.

A manual testing plan includes explicit regression checks for adjacent UI surfaces that may share code paths. It applies risk-focused validation to cover edge cases alongside the primary route-based verification steps.

You can use this QA plan for refactors requiring end-to-end browser verification. It applies to new features, bug fixes, and refactors by grounding the manual testing steps in the branch diff context and schema changes.

The generated testing plan does not include invented credentials or automated test commands. It produces strictly human-executable manual verification steps with concrete actors, actions, and expected results in a markdown file.

Write a testing plan markdown file by specifying the feature, bug fix, or refactor title for validation. The output generates required sections with concrete actors, actions, and expected results without needing manual formatting.