菜单
Generate structured test cases from BA acceptance criteria and Dev risk register. Use when QA needs to convert every AC into at least one verifiable test case with preconditions, steps, and expected results. Covers happy path, error cases, and edge cases for high-risk items.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | test-case-generator |
| description | Generate structured test cases from BA acceptance criteria and Dev risk register. Use when QA needs to convert every AC into at least one verifiable test case with preconditions, steps, and expected results. Covers happy path, error cases, and edge cases for high-risk items. |
| inclusion | manual |
Convert BA acceptance criteria and Dev risk items into structured, verifiable test cases — covering happy path, error handling, and edge cases.
acceptanceCriteria:
- "AC-001-1: GIVEN I am on the login page WHEN I click Forgot password and enter my registered email THEN the system sends a reset link within 60 seconds"
- "AC-001-3: GIVEN I click a reset link older than 24 hours WHEN the page loads THEN the system shows 'This link has expired'"
risks:
- "RISK-001: Token not invalidated after use — user could reuse a reset link"
### TC-001: Password reset email sent successfully
- **Related requirement**: AC-001-1
- **Preconditions**: User account exists with email user@example.com; user is on the login page
- **Steps**:
1. Click "Forgot password" link
2. Enter "user@example.com" in the email field
3. Click "Send Reset Link"
- **Expected result**: Success message displayed; reset email arrives in inbox within 60 seconds; email contains a valid reset link
- **Status**: pending
---
### TC-002: Expired reset link shows error
- **Related requirement**: AC-001-3
- **Preconditions**: A password reset link was generated more than 24 hours ago and has not been used
- **Steps**:
1. Open the expired reset link in a browser
- **Expected result**: Page displays "This link has expired" message with an option to request a new reset link; no password change is possible
- **Status**: pending
---
### TC-003: Used reset link cannot be reused (security)
- **Related requirement**: AC-001-2 | **Risk**: RISK-001
- **Preconditions**: User has successfully reset their password using a valid reset link
- **Steps**:
1. Copy the reset link URL before using it
2. Complete the password reset successfully
3. Navigate back to the copied reset link URL
- **Expected result**: System shows "This link has already been used" or equivalent error; password cannot be changed again with the same link
- **Status**: pending
| Source | Minimum Coverage |
|---|---|
| Each AC | At least 1 test case (happy path) |
| Each AC with error condition | At least 1 additional error test case |
| Each 🔴 Critical risk | At least 2 test cases (trigger + boundary) |
| Each 🟡 Medium risk | At least 1 test case |
| Type | When to Write |
|---|---|
| Happy path | Every AC — the normal successful flow |
| Error handling | ACs with explicit error conditions (expired, invalid, missing) |
| Boundary | Numeric limits, time thresholds, max lengths |
| Security | Auth bypass, token reuse, privilege escalation, enumeration |
| Edge case | Empty states, concurrent actions, network interruption |
当用户要求估时间、评估开发工作量、需求评估、 或提到"这个需求要多久""帮我估一下""评估一下工作量""开发时间"时激活。 结合需求材料（文档/截图/链接/描述）、项目代码结构和业务上下文， 分析需要做哪些事情，给出 AI 辅助开发下的参考开发时间估算。
追问会话，挑战你的计划与现有领域模型的一致性，锐化术语，并在决策明确时内联更新文档（CONTEXT.md、ADR）。当用户想要针对项目语言和已记录决策来压力测试计划时使用。
Execute test cases against a codebase and collect structured results. Use when test cases are ready and need to be run, when verifying a fix resolves a failing test, or when generating a test execution report.
A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution.
Analyze competitors with feature comparison matrices, positioning analysis, and strategic implications. Use when researching a competitor, comparing product capabilities, assessing competitive positioning, or preparing a competitive brief for product strategy.
Write robust C# avoiding null traps, async deadlocks, and LINQ pitfalls.