VS Test Case Generator

Problem

Turning requirement docs, rules, or screenshots into test cases often suffers from scope drift, missed scenarios, and hard-to-review output. vs-testcase-generator breaks generation into confirmable checkpoints: lock the module, confirm the mind map, then write the table, avoiding uncontrolled one-shot generation.

How It Works

• Module selection: extracts modules from the input and waits for a number, multiple numbers, or all; if a module is already named, it restates the locked scope.
• Mind-map confirmation: outputs a fixed Test Case Mind Map with module → scene → test point; test methods follow test point: -> and uncertain items are marked [pending].
• Template output: uses the default four-table template to generate scenes/cases JSON, write Excel, and run stats/self-checks; it can also parse a custom template and validate field mapping before filling it.
• Direct iteration: V1.1+ changes follow explicit user feedback; the default template auto-bumps the minor version, syncs the cover, appends version history, and reruns self-checks.
• Delivery checks: reports output path, scene/case counts, P0-P3 distribution, positive/negative ratio, orphan cases, isolated scenes, and self-check status; issues pause the flow with next steps.

Scope

It fits first drafts and iterative test cases built from requirements, feature notes, or rule descriptions. Custom templates must not alter headers, column order, formula columns, hidden columns, or protected columns; failed image recognition, ambiguous fields, or self-check failures require manual confirmation instead of guessing.