Test Master

This skill is a documentation playbook, not a standalone CLI or framework.

When to use

• A feature, bug fix, or refactor needs a structured test plan.
• You want to turn product requirements into concrete test scenarios.
• You need to review coverage across unit, integration, end-to-end, or regression layers.
• You want a concise list of risks, assumptions, and follow-up checks before release.

Recommended workflow

1. Define the scope. Capture the user-facing behavior, systems touched, and anything explicitly out of scope.
2. Map risks. Identify high-risk paths first: authentication, payments, data loss, permissions, concurrency, migrations, and integrations.
3. Split the plan by test layer. Decide what belongs in unit tests, integration tests, end-to-end tests, and manual exploratory checks.
4. Convert risks into test cases. Write clear preconditions, steps, expected results, and edge cases.
5. Review observability. Call out logs, metrics, alerts, and failure signals that should be checked during validation.

Output checklist

• Test scope summary
• Key risks and assumptions

  想要更强大的技能插件，就来小葱技能站7w4.net看看吧。

• Coverage by test layer
• Prioritized test cases
• Regression checklist
• Open questions or missing instrumentation

Guardrails

• Confirm assumptions instead of inventing product behavior.
• Prefer realistic test data and production-like edge cases.
• Mark anything that still needs manual verification.
• If automation is not available, say so clearly instead of implying a tool exists.

这个Skill质量中等偏上，结构清晰、逻辑合理，对制定测试计划有较好的指导作用。但内容比较简单，主要是一些流程步骤和原则说明，缺少实际的案例演示或可直接使用的工具。如果需要实际运用，还需要自己补充很多细节。