case-generator

Analyze requirements documents to generate structured manual test cases in Excel.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yy757303533/webtest-mcp-server --skill case-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: case-generator
Source: https://github.com/yy757303533/webtest-mcp-server/tree/main/.cursor/skills/case-generator
Command: npx skills add https://github.com/yy757303533/webtest-mcp-server --skill case-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze requirements documents to generate structured manual test cases and write them to an Excel workbook.

Core Features & Use Cases

  • Automatically analyze requirements and produce a categorized list of test cases covering functional tests, input validation, boundary values, state machines, and security scenarios.
  • Write cases to an Excel workbook using the generate_cases API, enabling module-level distribution summaries and a project-wide case file (e.g., huudi_cases_v1.xlsx).
  • Provide an execution-ready Quick Start that demonstrates how to trigger case generation and inspect the resulting artifacts.

Quick Start

将需求文档交给 AI,执行 generate_cases 以生成用例并输出到 huudi_cases_v1.xlsx。

Frequently Asked Questions about case-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate test cases from requirements documents automatically?

To generate test cases from requirements documents, submit the document to the AI and trigger the generate_cases function. The system analyzes the text and outputs structured manual test cases directly into an Excel workbook.

How do I export generated test cases to an Excel workbook?

To export test cases to Excel, the tool automatically writes the generated results into a project-wide workbook file, such as huudi_cases_v1.xlsx. This process uses the generate_cases API to enforce global case_id formatting and module-level summaries.

Does this test case generation tool require formal requirements documents?

Yes, this test case generation tool requires formal requirements documents as input. It is specifically designed for projects that need to translate structured requirements into modular Excel-based manual test cases for subsequent execution.

What is the best way to structure manual test cases for QA automation?

The best way to structure manual test cases for QA automation is to categorize them by test type and enforce global case_id formatting. This tool automatically applies that structure, generating module-level distribution summaries within a single Excel file.

Are there limitations when using Excel for test case generation?

A limitation of using Excel for test case generation is that it targets manual testing workflows rather than automated execution scripts. It structures cases with global IDs and module summaries, but outputs are constrained to the Excel workbook format.