AI Agent Hub
Back to skills
Test Case Design Assistant icon

Test Case Design Assistant

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Install @user_15292d5a/yjkj-test-case-design into the current AI assistant using https://skillhub.cn/install/skillhub.md.

About this skill

Problem

After requirements are reviewed, teams often need to draft functional, API, or agent test cases from scratch. Rules, edge cases, and platform differences are easy to miss, and inconsistent output slows review. This skill turns test case generation into a file-driven workflow with explicit type selection, capability loading, platform overlays, self-check, and table output.

Workflow

  • Type selection: use API wording for api-testing.md, agent wording for agent-testing.md plus functional design rules and quality standards, otherwise use functional testing.
  • File loading: always load templates/common-rules.md, then choose capability files by type.
  • Platform overlay: mobile, mini-program, mobile web, desktop, and PC web keywords load the matching platform/*.md files.
  • Self-check and output: validate against the relevant checklist and emit a Markdown table using examples/format-spec.md.

Boundaries

It generates test cases, not test plans, strategies, penetration execution, vulnerability scanning, load or stress testing, or automation scripts.

Use Cases

  • Generate API test cases before acceptance by covering parameters, error codes, authentication, and edge conditions.
  • Prepare agent test cases around user goals, tool calls, failure fallbacks, and quality standards during agent feature review.
  • Add platform-specific test points for mini-program authorization, payment, sharing, navigation, and subscription flows.
  • Draft functional test cases for PC web forms, routing, drag-and-drop, and keyboard flows before regression review.

Best For

  • API testers who need complete parameter, error, and authentication cases for interface acceptance.
  • Agent product QA owners who need coverage of tool calls, context failures, and business goal completion.
  • Mini-program or H5 testers who need authorization, payment, navigation, and similar platform-specific points.
  • Functional testers who need a consistent table for feature cases and platform checklist items.