Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Kokxi/qa-test-skills --skill qa-test-case-designgit clone --depth 1 https://github.com/Kokxi/qa-test-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kokxi/qa-test-skills/qa-test-case-design)<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-test-case-design"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-test-case-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-test-case-design"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-test-case-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00123 | $0.02681 |
| Opus 5 | $0.00062 | $0.01340 |
| Sonnet 5 | $0.00025 | $0.00536 |
| Haiku 4.5 | $0.00012 | $0.00268 |
Grade A, and why
qa-test-case-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
高级测试用例设计专项
核心原则
测试用例设计的核心——明确"测什么"，而非"怎么测"。
我们专注于：用例结构设计、场景覆盖策略、分类优先级、测试点识别组织。
重要限制：禁止读取代码——测试用例必须基于需求文档，不得读取代码实现。确保验证"系统应该做什么"，而非"系统如何实现"。
详细的设计方法、覆盖策略和评审标准参见
references/目录：
references/design-methods.md— 10种设计方法详解 + 复杂场景覆盖references/coverage-and-quality.md— 覆盖维度 + 质量指标references/review-standards.md— 需求文档要求 + 评审标准
设计理念
为什么测试步骤留空？
同一个"登录"功能，不同系统实现完全不同。
AI不知道你们系统用的是哪种实现方式：
- 强制生成步骤 → 步骤与实际不符 → 测试人员需要大量修正 → 增加工作量
- 测试步骤留空 → 用户基于实际系统补充 → 只需补充细节 → 减少工作量
测试用例结构设计
重要：输出格式、用例分级、编号规则是固定的，必须严格遵守。
标准用例字段模板
📖 完整的字段模板、用例编号规则、级别定义、输出格式和报告结构详见
references/output-template-full.md。本节保留核心字段概览，详细模板按需加载以节省 context。
使用方法
触发场景
当用户提供以下类型的请求时，此技能自动激活：
- 生成测试用例："帮我设计用户登录功能的测试用例"
- 完善用例："这些测试用例不够全面，请补充异常场景"
- 审查用例："检查一下这些测试用例是否有遗漏"
- 评审辅助："我需要准备测试用例评审，生成一套完整的用例"
- 覆盖优化："这个功能还缺哪些测试场景"
- 质量评估："评估一下这些测试用例的质量"
输入要素
为生成高质量的测试用例，尽量提供以下信息：
- 需求描述：功能需求的详细说明
- 业务背景：该功能在整体产品中的定位
- 约束条件：技术限制、合规要求等
- 目标用户：主要使用人群及其特征
- 关联系统：涉及的其他模块或第三方服务
- 风险点：已知的高风险区域
- 历史缺陷：类似功能的历史问题
输出内容
- 完整测试用例集：涵盖所有识别出的测试点
- 测试优先级排序：按P0-P3分级展示
- 覆盖率说明：已覆盖的测试维度列表
- 缺失风险提示：可能存在的测试盲区建议
- 测试建议：针对测试执行的建议
最佳实践
用例设计原则
✅ DO - 推荐做法
- 每个用例只验证一个明确的目标
- 使用清晰的数字序号标记预期结果
- 预期结果使用"应该/必须/会"等确定性词汇
- 包含正向和反向两种情况的验证
- 标注敏感信息的脱敏处理方式
- 为复杂场景添加截图或伪代码说明
- 测试步骤留空，由用户根据实际系统补充
❌ DON'T - 避免做法
- 模糊的描述如"检查是否可以正常工作"
- 一次性验证过多无关功能
- 忽略前置条件和环境配置
- 混合多个验证点在一个预期结果中
- 使用主观判断代替客观测量
- 忽略异常处理流程
- 强制生成可能与实际不符的测试步骤
用例评审要点
- 完整性检查：是否覆盖所有需求点和隐性场景
- 独立性检查：用例之间是否存在强依赖关系
- 可执行性检查：预期结果是否清晰、客观可测量
- 可维护性检查：命名规范、变更可追溯
- 优先级合理性：P0用例是否真正关键
- 覆盖全面性：功能、数据、权限、集成是否覆盖
输出示例
示例1：电商下单功能测试用例设计
## 订单模块 - 商品下单 - P0
### TC_ORDER_CREATE_001 正常下单流程
**测试类型**: 功能测试
**功能模块**: 订单管理
**子功能**: 商品下单
**用例级别**: P0
**预置条件**:
1. 用户已登录且账户余额充足
2. 商品库存大于0
3. 收货地址已配置
**测试步骤**:
（留空，由用户根据实际系统补充）
**预期结果**:
1. 进入订单确认页
2. 订单金额计算准确（含运费优惠）
3. 订单创建成功，返回订单号
4. 库存扣减正确
5. 收到订单confirmation通知
**实际结果**: 待执行
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago Changed cd4cc3bde8d5
- 10d ago First seen · 261 lines · 123 tokens per session scan A 81f216bbb589
qa-test-case-design is a skill published in the GitHub repository Kokxi/qa-test-skills (25 stars, last pushed 7d ago), licensed MIT. It adds 123 tokens to every session and 2,681 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
octocode-benchmark
Use when planning, running, grading, or reporting the by-hand Octocode research benchmark — pairwise matchups (Octocode anchor vs one baseline: gh+RTK, gh+Headroom, or plain gh) over markdown questions, with a fresh isolated runner agent per (question, arm, pass), one blind judge per question grading two answers X/Y…
octocode-graph-eval
Use when you need a measurable keep/discard loop — goal→KPI, baseline vs target, held-out checks, eval suites, or don't-stop-till-done against a runnable sensor. Not for ordinary ship checks where 'tests passed' is enough.
plugin-test
A testing guide for Zhin.js plugins using Vitest, a JavaScript and TypeScript testing framework. It focuses on checking command and tool behavior, ordinary business logic, and the plugin package’s required structure.