QA Test Planner

QA测试规划工具

A comprehensive skill for QA engineers to create test plans, generate manual test cases, build regression test suites, validate designs against Figma, and document bugs effectively.

Activation: This skill is triggered only when explicitly called by name (e.g.,
/qa-test-planner
,
qa-test-planner
, or
use the skill qa-test-planner
).

一款面向QA工程师的综合工具，可用于创建测试计划、生成手动测试用例、构建回归测试套件、对照Figma验证设计以及高效记录缺陷。

激活方式： 仅当通过名称显式调用时触发此工具（例如：
/qa-test-planner
、
qa-test-planner
或
use the skill qa-test-planner
）。

Quick Start

快速开始

Create a test plan:

"Create a test plan for the user authentication feature"

Generate test cases:

"Generate manual test cases for the checkout flow"

Build regression suite:

"Build a regression test suite for the payment module"

Validate against Figma:

"Compare the login page against the Figma design at [URL]"

Create bug report:

"Create a bug report for the form validation issue"

创建测试计划：

"为用户认证功能创建测试计划"

生成测试用例：

"为结账流程生成手动测试用例"

构建回归测试套件：

"为支付模块构建回归测试套件"

对照Figma验证：

"将登录页与[URL]处的Figma设计进行对比"

创建缺陷报告：

"为表单验证问题创建缺陷报告"

Quick Reference

快速参考

Task	What You Get	Time
Test Plan	Strategy, scope, schedule, risks	10-15 min
Test Cases	Step-by-step instructions, expected results	5-10 min each
Regression Suite	Smoke tests, critical paths, execution order	15-20 min
Figma Validation	Design-implementation comparison, discrepancy list	10-15 min
Bug Report	Reproducible steps, environment, evidence	5 min

任务	输出内容	耗时
测试计划	策略、范围、进度安排、风险	10-15分钟
测试用例	分步操作说明、预期结果	每个5-10分钟
回归测试套件	冒烟测试、关键路径、执行顺序	15-20分钟
Figma验证	设计与实现对比、差异列表	10-15分钟
缺陷报告	可复现步骤、环境信息、证据	5分钟

How It Works

工作原理

Your Request
    │
    ▼
┌─────────────────────────────────────────────────────┐
│ 1. ANALYZE                                          │
│    • Parse feature/requirement                      │
│    • Identify test types needed                     │
│    • Determine scope and priorities                 │
├─────────────────────────────────────────────────────┤
│ 2. GENERATE                                         │
│    • Create structured deliverables                 │
│    • Apply templates and best practices             │
│    • Include edge cases and variations              │
├─────────────────────────────────────────────────────┤
│ 3. VALIDATE                                         │
│    • Check completeness                             │
│    • Verify traceability                            │
│    • Ensure actionable steps                        │
└─────────────────────────────────────────────────────┘
    │
    ▼
QA Deliverable Ready

用户请求
    │
    ▼
┌─────────────────────────────────────────────────────┐
│ 1. 分析                                          │
│    • 解析功能/需求                      │
│    • 确定所需测试类型                     │
│    • 明确范围与优先级                 │
├─────────────────────────────────────────────────────┤
│ 2. 生成                                         │
│    • 创建结构化交付产物                 │
│    • 应用模板与最佳实践             │
│    • 包含边缘情况与变体              │
├─────────────────────────────────────────────────────┤
│ 3. 验证                                         │
│    • 检查完整性                             │
│    • 验证可追溯性                            │
│    • 确保步骤可执行                        │
└─────────────────────────────────────────────────────┘
    │
    ▼
QA交付产物已就绪

Commands

命令

Interactive Scripts

交互式脚本

Script	Purpose	Usage
`./scripts/generate_test_cases.sh`	Create test cases interactively	Step-by-step prompts
`./scripts/create_bug_report.sh`	Generate bug reports	Guided input collection

脚本	用途	使用方式
`./scripts/generate_test_cases.sh`	交互式创建测试用例	分步提示引导
`./scripts/create_bug_report.sh`	生成缺陷报告	引导式信息收集

Natural Language

自然语言指令

Request	Output
"Create test plan for {feature}"	Complete test plan document
"Generate {N} test cases for {feature}"	Numbered test cases with steps
"Build smoke test suite"	Critical path tests
"Compare with Figma at {URL}"	Visual validation checklist
"Document bug: {description}"	Structured bug report

请求	输出
"为{功能}创建测试计划"	完整的测试计划文档
"为{功能}生成{N}个测试用例"	带步骤的编号测试用例
"构建冒烟测试套件"	关键路径测试用例
"与{URL}处的Figma设计进行对比"	视觉验证检查清单
"记录缺陷：{描述}"	结构化缺陷报告

Core Deliverables

核心交付产物

1. Test Plans

1. 测试计划

Test scope and objectives
Testing approach and strategy
Environment requirements
Entry/exit criteria
Risk assessment
Timeline and milestones

测试范围与目标
测试方法与策略
环境要求
进入/退出标准
风险评估
时间线与里程碑

2. Manual Test Cases

2. 手动测试用例

Step-by-step instructions
Expected vs actual results
Preconditions and setup
Test data requirements
Priority and severity

分步操作说明
预期结果 vs 实际结果
前置条件与准备工作
测试数据要求
优先级与严重程度

3. Regression Suites

3. 回归测试套件

Smoke tests (15-30 min)
Full regression (2-4 hours)
Targeted regression (30-60 min)
Execution order and dependencies

冒烟测试（15-30分钟）
完整回归测试（2-4小时）
针对性回归测试（30-60分钟）
执行顺序与依赖关系

4. Figma Validation

4. Figma验证

Component-by-component comparison
Spacing and typography checks
Color and visual consistency
Interactive state validation

逐组件对比
间距与排版检查
颜色与视觉一致性
交互状态验证

5. Bug Reports

5. 缺陷报告

Clear reproduction steps
Environment details
Evidence (screenshots, logs)
Severity and priority

清晰的复现步骤
环境详情
证据（截图、日志）
严重程度与优先级

Anti-Patterns

反模式

Avoid	Why	Instead
Vague test steps	Can't reproduce	Specific actions + expected results
Missing preconditions	Tests fail unexpectedly	Document all setup requirements
No test data	Tester blocked	Provide sample data or generation
Generic bug titles	Hard to track	Specific: "[Feature] issue when [action]"
Skip edge cases	Miss critical bugs	Include boundary values, nulls

需避免的做法	原因	正确做法
模糊的测试步骤	无法复现	具体操作 + 预期结果
缺失前置条件	测试意外失败	记录所有准备要求
无测试数据	测试人员被阻塞	提供示例数据或生成方式
通用缺陷标题	难以追踪	具体化："[功能]执行[操作]时出现问题"
忽略边缘情况	遗漏关键缺陷	包含边界值、空值等情况

Verification Checklist

验证检查清单

References

参考资料

Test Case Templates - Standard formats for all test types
Bug Report Templates - Documentation templates
Regression Testing Guide - Suite building and execution
Figma Validation Guide - Design-implementation validation

<details> <summary>Deep Dive: Test Case Structure</summary>

测试用例模板 - 适用于所有测试类型的标准格式
缺陷报告模板 - 文档模板
回归测试指南 - 套件构建与执行说明
Figma验证指南 - 设计与实现验证说明

<details> <summary>深入解析：测试用例结构</summary>

Standard Test Case Format

标准测试用例格式

markdown

undefined

markdown

undefined

TC-001: [Test Case Title]

TC-001: [测试用例标题]

Objective

[What are we testing and why]

[测试内容及目的]

Preconditions

[Setup requirement 1]
[Setup requirement 2]
[Test data needed]

[准备要求1]
[准备要求2]
[所需测试数据]

Test Steps

[Action to perform] Expected: [What should happen]
[Action to perform] Expected: [What should happen]
[Action to perform] Expected: [What should happen]

[执行操作] Expected: [预期结果]
[执行操作] Expected: [预期结果]
[执行操作] Expected: [预期结果]

Test Data

Input: [Test data values]
User: [Test account details]
Configuration: [Environment settings]

Input: [测试数据值]
User: [测试账户详情]
Configuration: [环境设置]

Post-conditions

[System state after test]
[Cleanup required]

[测试后的系统状态]
[所需清理操作]

Notes

[Edge cases to consider]
[Related test cases]
[Known issues]

undefined

[需考虑的边缘情况]
[相关测试用例]
[已知问题]

undefined

Test Types

测试类型

Type	Focus	Example
Functional	Business logic	Login with valid credentials
UI/Visual	Appearance, layout	Button matches Figma design
Integration	Component interaction	API returns data to frontend
Regression	Existing functionality	Previous features still work
Performance	Speed, load handling	Page loads under 3 seconds
Security	Vulnerabilities	SQL injection prevented

</details> <details> <summary>Deep Dive: Test Plan Template</summary>

类型	关注点	示例
Functional	业务逻辑	使用有效凭据登录
UI/Visual	外观、布局	按钮与Figma设计匹配
Integration	组件交互	API向前端返回数据
Regression	现有功能	之前的功能仍正常工作
Performance	速度、负载处理	页面加载时间低于3秒
Security	漏洞防护	防止SQL注入

</details> <details> <summary>深入解析：测试计划模板</summary>

Test Plan Structure

测试计划结构

markdown

undefined

markdown

undefined

Test Plan: [Feature/Release Name]

测试计划: [功能/版本名称]

Executive Summary

执行摘要

Feature/product being tested
Testing objectives
Key risks
Timeline overview

待测试的功能/产品
测试目标
关键风险
时间线概述

Test Scope

测试范围

In Scope:

Features to be tested
Test types (functional, UI, performance)
Platforms and environments
User flows and scenarios

Out of Scope:

Features not being tested
Known limitations
Third-party integrations (if applicable)

包含范围：

待测试功能
测试类型（功能、UI、性能）
平台与环境
用户流程与场景

排除范围：

不测试的功能
已知限制
第三方集成（如适用）

Test Strategy

测试策略

Test Types:

Manual testing
Exploratory testing
Regression testing
Integration testing
User acceptance testing

Test Approach:

Black box testing
Positive and negative testing
Boundary value analysis
Equivalence partitioning

测试类型：

手动测试
探索性测试
回归测试
集成测试
用户验收测试

测试方法：

黑盒测试
正向与反向测试
边界值分析
等价类划分

Test Environment

测试环境

Operating systems
Browsers and versions
Devices (mobile, tablet, desktop)
Test data requirements
Backend/API environments

操作系统
浏览器及版本
设备（移动端、平板、桌面端）
测试数据要求
后端/API环境

Entry Criteria

进入标准

Exit Criteria

退出标准

所有高优先级测试用例已执行
测试用例通过率达90%以上
所有关键缺陷已修复
无未解决的高严重程度缺陷
回归测试套件已通过

Risk Assessment

风险评估

Risk	Probability	Impact	Mitigation
[Risk 1]	H/M/L	H/M/L	[Mitigation]

风险	概率	影响	缓解措施
[风险1]	H/M/L	H/M/L	[缓解措施]

Test Deliverables

测试交付产物

Test plan document
Test cases
Test execution reports
Bug reports
Test summary report


</details>

<details>
<summary><strong>Deep Dive: Bug Reporting</strong></summary>

测试计划文档
测试用例
测试执行报告
缺陷报告
测试总结报告


</details>

<details>
<summary><strong>深入解析：缺陷报告</strong></summary>

Bug Report Template

缺陷报告模板

markdown

undefined

markdown

undefined

BUG-[ID]: [Clear, specific title]

BUG-[ID]: [清晰、具体的标题]

Environment

OS: [Windows 11, macOS 14, etc.]
Browser: [Chrome 120, Firefox 121, etc.]
Device: [Desktop, iPhone 15, etc.]
Build: [Version/commit]
URL: [Page where bug occurs]

OS: [Windows 11, macOS 14等]
Browser: [Chrome 120, Firefox 121等]
Device: [桌面端, iPhone 15等]
Build: [版本/提交记录]
URL: [缺陷出现的页面]

Description

[Clear, concise description of the issue]

[清晰、简洁的问题描述]

Steps to Reproduce

[Specific step]
[Specific step]
[Specific step]

[具体步骤]
[具体步骤]
[具体步骤]

Expected Behavior

[What should happen]

[预期结果]

Actual Behavior

[What actually happens]

[实际发生的情况]

Visual Evidence

Screenshot: [attached]
Video: [link if applicable]
Console errors: [paste errors]

Screenshot: [已附加]
Video: [链接（如适用）]
Console errors: [粘贴错误信息]

Impact

User Impact: [How many users affected]
Frequency: [Always, Sometimes, Rarely]
Workaround: [If one exists]

User Impact: [受影响用户数量]
Frequency: [总是、有时、很少]
Workaround: [是否有临时解决方法]

Additional Context

Related to: [Feature/ticket]
Regression: [Yes/No]
Figma design: [Link if UI bug]

undefined

Related to: [功能/工单]
Regression: [是/否]
Figma design: [链接（如为UI缺陷）]

undefined

Severity Definitions

严重程度定义

Level	Criteria	Examples
Critical (P0)	System crash, data loss, security	Payment fails, login broken
High (P1)	Major feature broken, no workaround	Search not working
Medium (P2)	Feature partial, workaround exists	Filter missing one option
Low (P3)	Cosmetic, rare edge cases	Typo, minor alignment

</details> <details> <summary>Deep Dive: Figma MCP Integration</summary>

级别	判定标准	示例
Critical (P0)	系统崩溃、数据丢失、安全问题	支付失败、登录功能损坏
High (P1)	主要功能损坏，无临时解决方法	搜索功能无法使用
Medium (P2)	功能部分可用，有临时解决方法	筛选功能缺少一个选项
Low (P3)	cosmetic问题、罕见边缘情况	拼写错误、轻微对齐问题

</details> <details> <summary>深入解析：Figma MCP集成</summary>

Design Validation Workflow

设计验证工作流

Prerequisites:

Figma MCP server configured
Access to Figma design files
Figma URLs for components/pages

Process:

Get Design Specs from Figma

"Get the button specifications from Figma file [URL]"

Response includes:
- Dimensions (width, height)
- Colors (background, text, border)
- Typography (font, size, weight)
- Spacing (padding, margin)
- Border radius
- States (default, hover, active, disabled)

Compare Implementation

TC: Primary Button Visual Validation
1. Inspect primary button in browser dev tools
2. Compare against Figma specs:
   - Dimensions: 120x40px
   - Border-radius: 8px
   - Background color: #0066FF
   - Font: 16px Medium #FFFFFF
3. Document discrepancies

Create Bug if Mismatch

BUG: Primary button color doesn't match design
Severity: Medium
Expected (Figma): #0066FF
Actual (Implementation): #0052CC
Screenshot: [attached]
Figma link: [specific component]

前置条件：

已配置Figma MCP服务器
有权限访问Figma设计文件
拥有组件/页面的Figma链接

流程：

从Figma获取设计规范

"从[链接]的Figma文件中获取按钮规范"

返回内容包括：
- 尺寸（宽、高）
- 颜色（背景色、文字色、边框色）
- 排版（字体、大小、字重）
- 间距（内边距、外边距）
- 边框圆角
- 状态（默认、悬停、激活、禁用）

对比实现效果

测试用例：主按钮视觉验证
1. 在浏览器开发者工具中检查主按钮
2. 与Figma规范对比：
   - 尺寸：120x40px
   - 边框圆角：8px
   - 背景色：#0066FF
   - 字体：16px Medium #FFFFFF
3. 记录差异

若不匹配则创建缺陷

缺陷：主按钮颜色与设计不符
严重程度：Medium
预期（Figma）：#0066FF
实际（实现）：#0052CC
截图：[已附加]
Figma链接：[具体组件]

What to Validate

验证内容

Element	What to Check	Tool
Colors	Hex values exact	Browser color picker
Spacing	Padding/margin px	DevTools computed styles
Typography	Font, size, weight	DevTools font panel
Layout	Width, height, position	DevTools box model
States	Hover, active, focus	Manual interaction
Responsive	Breakpoint behavior	DevTools device mode

元素	检查要点	工具
Colors	Hex值完全匹配	浏览器取色器
Spacing	内边距/外边距像素值	开发者工具计算样式
Typography	字体、大小、字重	开发者工具字体面板
Layout	宽、高、位置	开发者工具盒模型
States	悬停、激活、聚焦状态	手动交互
Responsive	断点行为	开发者工具设备模式

Example Queries

示例查询

"Get button specifications from Figma design [URL]"
"Compare navigation menu implementation against Figma design"
"Extract spacing values for dashboard layout from Figma"
"List all color tokens used in Figma design system"

</details> <details> <summary>Deep Dive: Regression Testing</summary>

"从[链接]的Figma设计中获取按钮规范"
"对比导航菜单实现效果与Figma设计"
"从Figma中提取仪表板布局的间距值"
"列出Figma设计系统中使用的所有颜色标记"

</details> <details> <summary>深入解析：回归测试</summary>

Suite Structure

套件结构

Suite Type	Duration	Frequency	Coverage
Smoke	15-30 min	Daily	Critical paths only
Targeted	30-60 min	Per change	Affected areas
Full	2-4 hours	Weekly/Release	Comprehensive
Sanity	10-15 min	After hotfix	Quick validation

套件类型	耗时	执行频率	覆盖范围
Smoke	15-30分钟	每日	仅关键路径
Targeted	30-60分钟	每次变更后	受影响区域
Full	2-4小时	每周/版本发布前	全面覆盖
Sanity	10-15分钟	热修复后	快速验证

Building a Regression Suite

构建回归测试套件

Step 1: Identify Critical Paths

What can users NOT live without?
What generates revenue?
What handles sensitive data?
What's used most frequently?

Step 2: Prioritize Test Cases

Priority	Description	Must Run
P0	Business-critical, security	Always
P1	Major features, common flows	Weekly+
P2	Minor features, edge cases	Releases

Step 3: Execution Order

Smoke first - if fails, stop and fix build
P0 tests next - must pass before proceeding
P1 then P2 - track all failures
Exploratory - find unexpected issues

步骤1：识别关键路径

用户不可或缺的功能是什么？
哪些功能产生收入？
哪些功能处理敏感数据？
哪些功能使用频率最高？

步骤2：测试用例优先级划分

优先级	描述	必须执行
P0	业务关键、安全相关	始终执行
P1	主要功能、常见流程	每周及以上
P2	次要功能、边缘情况	版本发布时

步骤3：执行顺序

先执行冒烟测试 - 若失败，停止并修复构建
然后执行P0测试 - 必须通过才能继续
接着执行P1和P2测试 - 追踪所有失败情况
探索性测试 - 发现意外问题

Pass/Fail Criteria

通过/失败标准

PASS:

All P0 tests pass
90%+ P1 tests pass
No critical bugs open

FAIL (Block Release):

Any P0 test fails
Critical bug discovered
Security vulnerability
Data loss scenario

CONDITIONAL:

P1 failures with workarounds
Known issues documented
Fix plan in place

</details> <details> <summary>Deep Dive: Test Execution Tracking</summary>

通过：

所有P0测试通过
90%以上P1测试通过
无未解决的关键缺陷

失败（阻止发布）：

任何P0测试失败
发现关键缺陷
存在安全漏洞
存在数据丢失场景

有条件通过：

P1测试失败但有临时解决方法
已知问题已记录
修复计划已制定

</details> <details> <summary>深入解析：测试执行追踪</summary>

Test Run Report Template

测试运行报告模板

markdown

undefined

markdown

undefined

Test Run: [Release Version]

测试运行: [版本号]

Date: 2024-01-15 Build: v2.5.0-rc1 Tester: [Name] Environment: Staging

Date: 2024-01-15 Build: v2.5.0-rc1 Tester: [姓名] Environment: Staging

Summary

摘要

Total Test Cases: 150
Executed: 145
Passed: 130
Failed: 10
Blocked: 5
Not Run: 5
Pass Rate: 90%

总测试用例数: 150
已执行: 145
通过: 130
失败: 10
阻塞: 5
未执行: 5
通过率: 90%

Test Cases by Priority

按优先级划分的测试用例

Priority	Total	Pass	Fail	Blocked
P0 (Critical)	25	23	2	0
P1 (High)	50	45	3	2
P2 (Medium)	50	45	3	2
P3 (Low)	25	17	2	1

优先级	总数	通过	失败	阻塞
P0 (Critical)	25	23	2	0
P1 (High)	50	45	3	2
P2 (Medium)	50	45	3	2
P3 (Low)	25	17	2	1

Critical Failures

关键失败项

TC-045: Payment processing fails
- Bug: BUG-234
- Status: Open

TC-045: 支付处理失败
- Bug: BUG-234
- Status: Open

Blocked Tests

阻塞的测试用例

TC-112: Dashboard widget (API endpoint down)

TC-112: 仪表板小部件（API端点不可用）

Risks

风险

2 critical bugs blocking release
Payment integration needs attention

2个关键缺陷阻止发布
支付集成需重点关注

Next Steps

下一步计划

Retest after BUG-234 fix
Complete remaining 5 test cases
Run full regression before sign-off

undefined

修复BUG-234后重新测试
完成剩余5个测试用例
发布前运行完整回归测试

undefined

Coverage Tracking

覆盖范围追踪

markdown

undefined

markdown

undefined

Coverage Matrix

覆盖范围矩阵

Feature	Requirements	Test Cases	Status	Gaps
Login	8	12	Complete	None
Checkout	15	10	Partial	Payment errors
Dashboard	12	15	Complete	None


</details>

<details>
<summary><strong>QA Process Workflow</strong></summary>

功能	需求数	测试用例数	状态	缺口
Login	8	12	已完成	无
Checkout	15	10	部分完成	支付错误相关
Dashboard	12	15	已完成	无


</details>

<details>
<summary><strong>QA流程工作流</strong></summary>

Phase 1: Planning

阶段1：规划

Phase 2: Test Design

阶段2：测试设计

Phase 3: Execution

阶段3：执行

Phase 4: Reporting

阶段4：报告

Compile test results
Analyze coverage
Document risks
Provide go/no-go recommendation
Archive test artifacts

</details> <details> <summary>Best Practices</summary>

整理测试结果
分析覆盖范围
记录风险
提供发布/不发布建议
归档测试产物

</details> <details> <summary>最佳实践</summary>

Test Case Writing

测试用例编写

DO:

Be specific and unambiguous
Include expected results for each step
Test one thing per test case
Use consistent naming conventions
Keep test cases maintainable

DON'T:

Assume knowledge
Make test cases too long
Skip preconditions
Forget edge cases
Leave expected results vague

建议：

具体明确，无歧义
每个步骤都包含预期结果
每个测试用例仅测试一个点
使用统一的命名规范
保持测试用例可维护

避免：

假设测试人员具备相关知识
测试用例过长
跳过前置条件
忽略边缘情况
预期结果模糊

Bug Reporting

缺陷报告

DO:

Provide clear reproduction steps
Include screenshots/videos
Specify exact environment details
Describe impact on users
Link to Figma for UI bugs

DON'T:

Report without reproduction steps
Use vague descriptions
Skip environment details
Forget to assign priority
Duplicate existing bugs

建议：

提供清晰的复现步骤
包含截图/视频
指定精确的环境详情
描述对用户的影响
UI缺陷关联Figma链接

避免：

无复现步骤的缺陷报告
使用模糊描述
跳过环境详情
忘记分配优先级
重复报告已存在的缺陷

Regression Testing

回归测试

DO:

Automate repetitive tests when possible
Maintain regression suite regularly
Prioritize critical paths
Run smoke tests frequently
Update suite after each release

DON'T:

Skip regression before releases
Let suite become outdated
Test everything every time
Ignore failed regression tests

</details>

建议：

尽可能自动化重复测试
定期维护回归测试套件
优先覆盖关键路径
频繁运行冒烟测试
每次版本发布后更新套件

避免：

发布前跳过回归测试
让套件过时
每次都测试所有内容
忽略失败的回归测试

</details>

Examples

示例

<details> <summary>Example: Login Flow Test Case</summary>

markdown

undefined

<details> <summary>示例：登录流程测试用例</summary>

markdown

undefined

TC-LOGIN-001: Valid User Login

TC-LOGIN-001: 有效用户登录

Priority: P0 (Critical) Type: Functional Estimated Time: 2 minutes

Objective

Verify users can successfully login with valid credentials

验证用户可使用有效凭据成功登录

Preconditions

User account exists (test@example.com / Test123!)
User is not already logged in
Browser cookies cleared

用户账户已存在（test@example.com / Test123!）
用户当前未登录
浏览器Cookie已清除

Test Steps

Navigate to https://app.example.com/login Expected: Login page displays with email and password fields
Enter email: test@example.com Expected: Email field accepts input
Enter password: Test123! Expected: Password field shows masked characters
Click "Login" button Expected:
- Loading indicator appears
- User redirected to /dashboard
- Welcome message shown: "Welcome back, Test User"
- Avatar/profile image displayed in header

导航至https://app.example.com/login Expected: 登录页显示邮箱和密码输入框
输入邮箱: test@example.com Expected: 邮箱字段接受输入
输入密码: Test123! Expected: 密码字段显示掩码字符
点击"Login"按钮 Expected:
- 出现加载指示器
- 用户被重定向至/dashboard
- 显示欢迎消息: "Welcome back, Test User"
- 头像/个人资料图片显示在页眉

Post-conditions

User session created
Auth token stored
Analytics event logged

用户会话已创建
认证令牌已存储
已记录分析事件

Edge Cases to Consider

TC-LOGIN-002: Invalid password
TC-LOGIN-003: Non-existent email
TC-LOGIN-004: SQL injection attempt
TC-LOGIN-005: Very long password


</details>

<details>
<summary><strong>Example: Responsive Design Test Case</strong></summary>

```markdown

TC-LOGIN-002: 无效密码
TC-LOGIN-003: 不存在的邮箱
TC-LOGIN-004: SQL注入尝试
TC-LOGIN-005: 超长密码


</details>

<details>
<summary><strong>示例：响应式设计测试用例</strong></summary>

```markdown

TC-UI-045: Mobile Navigation Menu

TC-UI-045: 移动端导航菜单

Priority: P1 (High) Type: UI/Responsive Devices: Mobile (iPhone, Android)

Objective

Verify navigation menu works correctly on mobile devices

验证导航菜单在移动设备上正常工作

Preconditions

Access from mobile device or responsive mode
Viewport width: 375px (iPhone SE) to 428px (iPhone Pro Max)

从移动设备或响应式模式访问
视口宽度: 375px (iPhone SE) 至 428px (iPhone Pro Max)

Test Steps

Open homepage on mobile device Expected: Hamburger menu icon visible (top-right)
Tap hamburger icon Expected:
- Menu slides in from right
- Overlay appears over content
- Close (X) button visible
Tap menu item Expected: Navigate to section, menu closes
Compare against Figma mobile design [link] Expected:
- Menu width: 280px
- Slide animation: 300ms ease-out
- Overlay opacity: 0.5, color #000000
- Font size: 16px, line-height 24px

在移动设备上打开首页 Expected: 汉堡菜单图标显示在右上角
点击汉堡菜单图标 Expected:
- 菜单从右侧滑入
- 内容上方显示遮罩层
- 显示关闭（X）按钮
点击菜单项 Expected: 跳转到对应板块，菜单关闭
与[链接]的Figma移动端设计对比 Expected:
- 菜单宽度: 280px
- 滑动动画: 300ms ease-out
- 遮罩层透明度: 0.5, 颜色#000000
- 字体大小: 16px, line-height 24px

Breakpoints to Test

375px (iPhone SE)
390px (iPhone 14)
428px (iPhone 14 Pro Max)
360px (Galaxy S21)


</details>

---

**"Testing shows the presence, not the absence of bugs." - Edsger Dijkstra**

**"Quality is not an act, it is a habit." - Aristotle**

375px (iPhone SE)
390px (iPhone 14)
428px (iPhone 14 Pro Max)
360px (Galaxy S21)


</details>

---

**"Testing shows the presence, not the absence of bugs." - Edsger Dijkstra**

**"Quality is not an act, it is a habit." - Aristotle**

qa-test-planner

Original

Translation

QA Test Planner

QA测试规划工具

Quick Start

快速开始

Quick Reference

快速参考

How It Works

工作原理

Commands

命令

Interactive Scripts

交互式脚本

Natural Language

自然语言指令

Core Deliverables

核心交付产物

1. Test Plans

1. 测试计划

2. Manual Test Cases

2. 手动测试用例

3. Regression Suites

3. 回归测试套件

4. Figma Validation

4. Figma验证

5. Bug Reports

5. 缺陷报告

Anti-Patterns

反模式

Verification Checklist

验证检查清单

References

参考资料

Standard Test Case Format

标准测试用例格式

TC-001: [Test Case Title]

TC-001: [测试用例标题]

Objective

Objective

Preconditions

Preconditions

Test Steps

Test Steps

Test Data

Test Data

Post-conditions

Post-conditions

Notes

Notes

Test Types

测试类型

Test Plan Structure

测试计划结构

Test Plan: [Feature/Release Name]

测试计划: [功能/版本名称]

Executive Summary

执行摘要

Test Scope

测试范围

Test Strategy

测试策略

Test Environment

测试环境

Entry Criteria

进入标准

Exit Criteria

退出标准

Risk Assessment

风险评估

Test Deliverables

测试交付产物

Bug Report Template

缺陷报告模板

BUG-[ID]: [Clear, specific title]

BUG-[ID]: [清晰、具体的标题]

Environment

Environment

Description