qa-test-planner by softaworks/agent-toolkit
npx skills add https://github.com/softaworks/agent-toolkit --skill qa-test-planner一款为 QA 工程师设计的综合性技能,用于创建测试计划、生成手动测试用例、构建回归测试套件、根据 Figma 验证设计以及有效记录缺陷。
激活方式: 此技能仅在明确按名称调用时触发(例如
/qa-test-planner、qa-test-planner或use the skill qa-test-planner)。
创建测试计划:
"Create a test plan for the user authentication feature"
生成测试用例:
"Generate manual test cases for the checkout flow"
构建回归套件:
"Build a regression test suite for the payment module"
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
"Compare the login page against the Figma design at [URL]"
创建缺陷报告:
"Create a bug report for the form validation issue"
| 任务 | 你将获得 | 耗时 |
|---|---|---|
| 测试计划 | 策略、范围、时间表、风险 | 10-15 分钟 |
| 测试用例 | 分步说明、预期结果 | 每个 5-10 分钟 |
| 回归套件 | 冒烟测试、关键路径、执行顺序 | 15-20 分钟 |
| Figma 验证 | 设计与实现对比、差异列表 | 10-15 分钟 |
| 缺陷报告 | 可复现步骤、环境、证据 | 5 分钟 |
Your Request
│
▼
┌─────────────────────────────────────────────────────┐
│ 1. 分析 │
│ • 解析功能/需求 │
│ • 识别所需测试类型 │
│ • 确定范围和优先级 │
├─────────────────────────────────────────────────────┤
│ 2. 生成 │
│ • 创建结构化的交付物 │
│ • 应用模板和最佳实践 │
│ • 包含边界情况和变体 │
├─────────────────────────────────────────────────────┤
│ 3. 验证 │
│ • 检查完整性 │
│ • 验证可追溯性 │
│ • 确保步骤可操作 │
└─────────────────────────────────────────────────────┘
│
▼
QA 交付物准备就绪
| 脚本 | 目的 | 用法 |
|---|---|---|
./scripts/generate_test_cases.sh | 交互式创建测试用例 | 分步提示 |
./scripts/create_bug_report.sh | 生成缺陷报告 | 引导式输入收集 |
| 请求 | 输出 |
|---|---|
| "Create test plan for {feature}" | 完整的测试计划文档 |
| "Generate {N} test cases for {feature}" | 带步骤的编号测试用例 |
| "Build smoke test suite" | 关键路径测试 |
| "Compare with Figma at {URL}" | 视觉验证检查清单 |
| "Document bug: {description}" | 结构化的缺陷报告 |
| 避免 | 原因 | 替代做法 |
|---|---|---|
| 模糊的测试步骤 | 无法复现 | 具体操作 + 预期结果 |
| 缺少前提条件 | 测试意外失败 | 记录所有设置要求 |
| 无测试数据 | 测试人员受阻 | 提供样本数据或生成方法 |
| 通用的缺陷标题 | 难以追踪 | 具体化:"[功能] 在 [操作] 时出现问题" |
| 忽略边界情况 | 遗漏关键缺陷 | 包含边界值、空值等 |
测试计划:
测试用例:
缺陷报告:
## TC-001: [测试用例标题]
**优先级:** High | Medium | Low
**类型:** Functional | UI | Integration | Regression
**状态:** Not Run | Pass | Fail | Blocked
### 目标
[我们测试什么以及为什么]
### 前提条件
- [设置要求 1]
- [设置要求 2]
- [所需测试数据]
### 测试步骤
1. [要执行的操作]
**预期:** [应该发生什么]
2. [要执行的操作]
**预期:** [应该发生什么]
3. [要执行的操作]
**预期:** [应该发生什么]
### 测试数据
- 输入: [测试数据值]
- 用户: [测试账户详情]
- 配置: [环境设置]
### 后置条件
- [测试后的系统状态]
- [所需的清理工作]
### 备注
- [需要考虑的边界情况]
- [相关的测试用例]
- [已知问题]
| 类型 | 关注点 | 示例 |
|---|---|---|
| 功能测试 | 业务逻辑 | 使用有效凭据登录 |
| UI/视觉测试 | 外观、布局 | 按钮与 Figma 设计匹配 |
| 集成测试 | 组件交互 | API 向前端返回数据 |
| 回归测试 | 现有功能 | 先前功能仍然有效 |
| 性能测试 | 速度、负载处理 | 页面在 3 秒内加载 |
| 安全测试 | 漏洞 | 防止 SQL 注入 |
# 测试计划: [功能/发布名称]
## 执行摘要
- 正在测试的功能/产品
- 测试目标
- 关键风险
- 时间线概述
## 测试范围
**范围内:**
- 要测试的功能
- 测试类型(功能、UI、性能)
- 平台和环境
- 用户流程和场景
**范围外:**
- 不测试的功能
- 已知限制
- 第三方集成(如适用)
## 测试策略
**测试类型:**
- 手动测试
- 探索性测试
- 回归测试
- 集成测试
- 用户验收测试
**测试方法:**
- 黑盒测试
- 正向和反向测试
- 边界值分析
- 等价类划分
## 测试环境
- 操作系统
- 浏览器和版本
- 设备(移动端、平板、桌面端)
- 测试数据要求
- 后端/API 环境
## 准入标准
- [ ] 需求已记录
- [ ] 设计已定稿
- [ ] 测试环境就绪
- [ ] 测试数据已准备
- [ ] 构建已部署
## 准出标准
- [ ] 所有高优先级测试用例已执行
- [ ] 测试用例通过率 90% 以上
- [ ] 所有严重缺陷已修复
- [ ] 无未解决的高严重性缺陷
- [ ] 回归套件通过
## 风险评估
| 风险 | 概率 | 影响 | 缓解措施 |
|------|-------------|--------|------------|
| [风险 1] | H/M/L | H/M/L | [缓解措施] |
## 测试交付物
- 测试计划文档
- 测试用例
- 测试执行报告
- 缺陷报告
- 测试总结报告
# BUG-[ID]: [清晰、具体的标题]
**严重性:** Critical | High | Medium | Low
**优先级:** P0 | P1 | P2 | P3
**类型:** Functional | UI | Performance | Security
**状态:** Open | In Progress | Fixed | Closed
## 环境
- **操作系统:** [Windows 11, macOS 14 等]
- **浏览器:** [Chrome 120, Firefox 121 等]
- **设备:** [桌面端, iPhone 15 等]
- **构建版本:** [版本/提交号]
- **URL:** [缺陷发生的页面]
## 描述
[对问题的清晰、简洁描述]
## 复现步骤
1. [具体步骤]
2. [具体步骤]
3. [具体步骤]
## 预期行为
[应该发生什么]
## 实际行为
[实际发生了什么]
## 视觉证据
- 截图: [已附上]
- 视频: [链接,如适用]
- 控制台错误: [粘贴错误信息]
## 影响
- **用户影响:** [有多少用户受影响]
- **频率:** [总是、有时、很少]
- **变通方案:** [如果存在]
## 附加信息
- 关联到: [功能/工单]
- 回归问题: [是/否]
- Figma 设计: [链接,如果是 UI 缺陷]
| 级别 | 标准 | 示例 |
|---|---|---|
| 严重 (P0) | 系统崩溃、数据丢失、安全 | 支付失败、登录功能损坏 |
| 高 (P1) | 主要功能损坏、无变通方案 | 搜索功能无法使用 |
| 中 (P2) | 功能部分可用、存在变通方案 | 筛选器缺少一个选项 |
| 低 (P3) | 外观问题、罕见的边界情况 | 拼写错误、轻微对齐问题 |
先决条件:
流程:
"Get the button specifications from Figma file [URL]"
响应包括:
- 尺寸(宽度、高度)
- 颜色(背景、文本、边框)
- 排版(字体、大小、粗细)
- 间距(内边距、外边距)
- 边框半径
- 状态(默认、悬停、激活、禁用)
2. 对比实现
TC: 主要按钮视觉验证
1. 在浏览器开发者工具中检查主要按钮
2. 与 Figma 规范对比:
- 尺寸: 120x40px
- 边框半径: 8px
- 背景颜色: #0066FF
- 字体: 16px Medium #FFFFFF
3. 记录差异
3. 如果不匹配则创建缺陷
BUG: 主要按钮颜色与设计不匹配
严重性: Medium
预期 (Figma): #0066FF
实际 (实现): #0052CC
截图: [已附上]
Figma 链接: [具体组件]
| 元素 | 检查内容 | 工具 |
|---|---|---|
| 颜色 | 十六进制值是否精确 | 浏览器取色器 |
| 间距 | 内边距/外边距像素值 | 开发者工具计算样式 |
| 排版 | 字体、大小、粗细 | 开发者工具字体面板 |
| 布局 | 宽度、高度、位置 | 开发者工具盒模型 |
| 状态 | 悬停、激活、焦点 | 手动交互 |
| 响应式 | 断点行为 | 开发者工具设备模式 |
"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"
| 套件类型 | 持续时间 | 频率 | 覆盖范围 |
|---|---|---|---|
| 冒烟测试 | 15-30 分钟 | 每日 | 仅关键路径 |
| 针对性测试 | 30-60 分钟 | 每次变更 | 受影响区域 |
| 完整测试 | 2-4 小时 | 每周/发布 | 全面覆盖 |
| 健全性测试 | 10-15 分钟 | 热修复后 | 快速验证 |
步骤 1:识别关键路径
步骤 2:确定测试用例优先级
| 优先级 | 描述 | 必须运行 |
|---|---|---|
| P0 | 业务关键、安全 | 总是 |
| P1 | 主要功能、常见流程 | 每周+ |
| P2 | 次要功能、边界情况 | 发布时 |
步骤 3:执行顺序
通过:
失败(阻止发布):
有条件通过:
# 测试运行: [发布版本]
**日期:** 2024-01-15
**构建版本:** v2.5.0-rc1
**测试人员:** [姓名]
**环境:** 预发布环境
## 摘要
- 总测试用例数: 150
- 已执行: 145
- 通过: 130
- 失败: 10
- 受阻: 5
- 未运行: 5
- 通过率: 90%
## 按优先级划分的测试用例
| 优先级 | 总数 | 通过 | 失败 | 受阻 |
|----------|-------|------|------|---------|
| P0 (严重) | 25 | 23 | 2 | 0 |
| P1 (高) | 50 | 45 | 3 | 2 |
| P2 (中) | 50 | 45 | 3 | 2 |
| P3 (低) | 25 | 17 | 2 | 1 |
## 严重失败
- TC-045: 支付处理失败
- 缺陷: BUG-234
- 状态: Open
## 受阻的测试
- TC-112: 仪表板小部件(API 端点宕机)
## 风险
- 2 个严重缺陷阻碍发布
- 支付集成需要关注
## 后续步骤
- BUG-234 修复后重新测试
- 完成剩余的 5 个测试用例
- 在签署前运行完整回归测试
## 覆盖率矩阵
| 功能 | 需求 | 测试用例 | 状态 | 差距 |
|---------|--------------|------------|--------|------|
| 登录 | 8 | 12 | 完成 | 无 |
| 结账 | 15 | 10 | 部分 | 支付错误 |
| 仪表板 | 12 | 15 | 完成 | 无 |
应该做:
不应该做:
应该做:
不应该做:
应该做:
不应该做:
## TC-LOGIN-001: 有效用户登录
**优先级:** P0 (严重)
**类型:** 功能测试
**预计时间:** 2 分钟
### 目标
验证用户可以使用有效凭据成功登录
### 前提条件
- 用户账户存在 (test@example.com / Test123!)
- 用户尚未登录
- 浏览器 Cookie 已清除
### 测试步骤
1. 导航到 https://app.example.com/login
**预期:** 登录页面显示,包含邮箱和密码字段
2. 输入邮箱: test@example.com
**预期:** 邮箱字段接受输入
3. 输入密码: Test123!
**预期:** 密码字段显示掩码字符
4. 点击"登录"按钮
**预期:**
- 出现加载指示器
- 用户重定向到 /dashboard
- 显示欢迎消息:"Welcome back, Test User"
- 头像/个人资料图片显示在页眉中
### 后置条件
- 用户会话已创建
- 认证令牌已存储
- 分析事件已记录
### 需要考虑的边界情况
- TC-LOGIN-002: 无效密码
- TC-LOGIN-003: 不存在的邮箱
- TC-LOGIN-004: SQL 注入尝试
- TC-LOGIN-005: 非常长的密码
## TC-UI-045: 移动端导航菜单
**优先级:** P1 (高)
**类型:** UI/响应式
**设备:** 移动端 (iPhone, Android)
### 目标
验证导航菜单在移动设备上正常工作
### 前提条件
- 从移动设备或响应式模式访问
- 视口宽度: 375px (iPhone SE) 到 428px (iPhone Pro Max)
### 测试步骤
1. 在移动设备上打开主页
**预期:** 汉堡菜单图标可见(右上角)
2. 点击汉堡图标
**预期:**
- 菜单从右侧滑入
- 内容上方出现覆盖层
- 关闭 (X) 按钮可见
3. 点击菜单项
**预期:** 导航到对应部分,菜单关闭
4. 与 Figma 移动端设计 [链接] 对比
**预期:**
- 菜单宽度: 280px
- 滑动动画: 300ms ease-out
- 覆盖层不透明度: 0.5, 颜色 #000000
- 字体大小: 16px, 行高 24px
### 需要测试的断点
- 375px (iPhone SE)
- 390px (iPhone 14)
- 428px (iPhone 14 Pro Max)
- 360px (Galaxy S21)
"测试只能证明缺陷存在,而不能证明缺陷不存在。" - Edsger Dijkstra
"质量不是一种行为,而是一种习惯。" - Aristotle
每周安装量
572
代码库
GitHub 星标数
1.2K
首次出现
Jan 20, 2026
安全审计
已安装于
codex417
gemini-cli417
cursor417
claude-code416
opencode400
cline398
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, oruse the skill qa-test-planner).
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"
| 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 |
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
| 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 |
| 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 |
| 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 |
Test Plan:
Test Cases:
Bug Reports:
## TC-001: [Test Case Title]
**Priority:** High | Medium | Low
**Type:** Functional | UI | Integration | Regression
**Status:** Not Run | Pass | Fail | Blocked
### Objective
[What are we testing and why]
### Preconditions
- [Setup requirement 1]
- [Setup requirement 2]
- [Test data needed]
### Test Steps
1. [Action to perform]
**Expected:** [What should happen]
2. [Action to perform]
**Expected:** [What should happen]
3. [Action to perform]
**Expected:** [What should happen]
### Test Data
- Input: [Test data values]
- User: [Test account details]
- Configuration: [Environment settings]
### Post-conditions
- [System state after test]
- [Cleanup required]
### Notes
- [Edge cases to consider]
- [Related test cases]
- [Known issues]
| 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 |
# 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)
## 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
## Entry Criteria
- [ ] Requirements documented
- [ ] Designs finalized
- [ ] Test environment ready
- [ ] Test data prepared
- [ ] Build deployed
## Exit Criteria
- [ ] All high-priority test cases executed
- [ ] 90%+ test case pass rate
- [ ] All critical bugs fixed
- [ ] No open high-severity bugs
- [ ] Regression suite passed
## Risk Assessment
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk 1] | H/M/L | H/M/L | [Mitigation] |
## Test Deliverables
- Test plan document
- Test cases
- Test execution reports
- Bug reports
- Test summary report
# BUG-[ID]: [Clear, specific title]
**Severity:** Critical | High | Medium | Low
**Priority:** P0 | P1 | P2 | P3
**Type:** Functional | UI | Performance | Security
**Status:** Open | In Progress | Fixed | Closed
## 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]
## Description
[Clear, concise description of the issue]
## Steps to Reproduce
1. [Specific step]
2. [Specific step]
3. [Specific step]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Visual Evidence
- Screenshot: [attached]
- Video: [link if applicable]
- Console errors: [paste errors]
## Impact
- **User Impact:** [How many users affected]
- **Frequency:** [Always, Sometimes, Rarely]
- **Workaround:** [If one exists]
## Additional Context
- Related to: [Feature/ticket]
- Regression: [Yes/No]
- Figma design: [Link if UI bug]
| 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 |
Prerequisites:
Process:
"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)
2. 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
3. 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]
| 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 |
"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"
| 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 |
Step 1: Identify Critical Paths
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
PASS:
FAIL (Block Release):
CONDITIONAL:
# Test Run: [Release Version]
**Date:** 2024-01-15
**Build:** v2.5.0-rc1
**Tester:** [Name]
**Environment:** Staging
## Summary
- Total Test Cases: 150
- Executed: 145
- Passed: 130
- Failed: 10
- Blocked: 5
- Not Run: 5
- Pass Rate: 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 |
## Critical Failures
- TC-045: Payment processing fails
- Bug: BUG-234
- Status: Open
## Blocked Tests
- TC-112: Dashboard widget (API endpoint down)
## Risks
- 2 critical bugs blocking release
- Payment integration needs attention
## Next Steps
- Retest after BUG-234 fix
- Complete remaining 5 test cases
- Run full regression before sign-off
## Coverage Matrix
| Feature | Requirements | Test Cases | Status | Gaps |
|---------|--------------|------------|--------|------|
| Login | 8 | 12 | Complete | None |
| Checkout | 15 | 10 | Partial | Payment errors |
| Dashboard | 12 | 15 | Complete | None |
DO:
DON'T:
DO:
DON'T:
DO:
DON'T:
## TC-LOGIN-001: Valid User Login
**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 Steps
1. Navigate to https://app.example.com/login
**Expected:** Login page displays with email and password fields
2. Enter email: test@example.com
**Expected:** Email field accepts input
3. Enter password: Test123!
**Expected:** Password field shows masked characters
4. Click "Login" button
**Expected:**
- Loading indicator appears
- User redirected to /dashboard
- Welcome message shown: "Welcome back, Test User"
- Avatar/profile image displayed in header
### 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
## TC-UI-045: Mobile Navigation Menu
**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)
### Test Steps
1. Open homepage on mobile device
**Expected:** Hamburger menu icon visible (top-right)
2. Tap hamburger icon
**Expected:**
- Menu slides in from right
- Overlay appears over content
- Close (X) button visible
3. Tap menu item
**Expected:** Navigate to section, menu closes
4. 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
### Breakpoints to Test
- 375px (iPhone SE)
- 390px (iPhone 14)
- 428px (iPhone 14 Pro Max)
- 360px (Galaxy S21)
"Testing shows the presence, not the absence of bugs." - Edsger Dijkstra
"Quality is not an act, it is a habit." - Aristotle
Weekly Installs
572
Repository
GitHub Stars
1.2K
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykWarn
Installed on
codex417
gemini-cli417
cursor417
claude-code416
opencode400
cline398
头脑风暴技能:AI协作设计流程,将创意转化为完整规范与实施计划
77,000 周安装
OpenAPI 转 TypeScript 工具 - 自动生成 API 接口与类型守卫
563 周安装
数据库模式设计器 - 内置最佳实践,自动生成生产级SQL/NoSQL数据库架构
564 周安装
Rust Unsafe代码检查器 - 安全使用Unsafe Rust的完整指南与最佳实践
564 周安装
.NET并发编程模式指南:async/await、Channels、Akka.NET选择决策树
565 周安装
韩语语法检查器 - 基于国立国语院标准的拼写、空格、语法、标点错误检测与纠正
565 周安装
技能安全扫描器 - 检测Claude技能安全漏洞,防范提示注入与恶意代码
565 周安装