test-gen

Generate structured test cases from code bases or acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pacvue/devflow-cursor --skill test-gen-pacvue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-gen
Source: https://github.com/Pacvue/devflow-cursor/tree/main/.cursor/skills/test-gen
Command: npx skills add https://github.com/Pacvue/devflow-cursor --skill test-gen-pacvue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

基于代码或接受标准(AC)自动生成测试用例,显著缩短 QA 的准备时间并提升覆盖率。

Core Features & Use Cases

  • 根据 AC 或代码基准自动构建测试用例,覆盖正向、负向和边界场景。
  • 支持从代码库中分析结构、生成带有 Test ID、标题、优先级、前提、步骤与期望结果等字段的用例集合。
  • 适用于快速验证新特性、回归测试以及在 CI/CD 流程中的测试草案生成。

Quick Start

直接让 AI 生成第一组测试用例,基于你提供的 AC 或目标代码库。

Frequently Asked Questions about test-gen

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

FAQPage Schema
How do I generate test cases from acceptance criteria automatically?

To auto-generate test cases from acceptance criteria, provide your AC or target codebase to the system. It selects a test basis, analyzes code structure, and outputs structured cases with IDs, titles, priorities, preconditions, steps, and expected results to accelerate QA validation.

Can I generate QA test cases directly from my source code repository?

Yes, you can generate QA test cases directly from a source code repository. The system clones repos when needed and analyzes the code structure to build structured test cases covering normal, negative, and boundary scenarios for regression or CI/CD validation.

What fields are included in the auto-generated test cases?

The auto-generated test cases include Test IDs, titles, priorities, preconditions, steps, and expected results. They are formatted using framework-agnostic templates and routed through a verifier to ensure coverage before being written to the output file.

Does the test generation process support integration with CI/CD pipelines?

Yes, the test generation process supports CI/CD pipelines by generating draft test cases for rapid feature validation and regression testing. It outputs framework-agnostic artifacts to a designated phase file, allowing seamless integration into automated validation workflows.

What is the best way to ensure test coverage when generating cases from a codebase?

The best way to ensure test coverage is routing the generated test cases through a verifier component. This validates that the structured cases cover positive, negative, and boundary scenarios derived from the analyzed code structure or acceptance criteria.

Are there limitations on hard-coding project names in the generated test cases?

Yes, a key limitation is that the system does not hard-code project names in the generated test cases. It uses framework-agnostic templates and writes final artifacts to a specific output file path to maintain project neutrality.