AI Agent Hub
Back to skills
Functional Test Case Designer icon

Functional Test Case Designer

Development Updated 2026.08.30

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

Please install @user_ab1ce028/functional-use-cases using the guide at https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Functional requirements often describe only the normal path, so test cases may miss boundary values, error recovery, concurrency, unsafe inputs, and cross-device compatibility. Game projects can also overlook skill tuning, pity mechanics, network sync, and localization.

How It Works

The skill starts from a requirements document or existing test cases, extracts features, business rules, inputs and outputs, and user scenarios, then applies methods such as boundary value analysis, equivalence partitioning, decision tables, and state transitions. It outputs Markdown tables with test ID, scenario, preconditions, steps, expected result, priority, and test dimension, grouped by functional, performance, security, usability, compatibility, and exception coverage.

Boundaries

It is best for test design, case review, and documentation backfill for web, mobile, and game systems with multi-platform or exception-heavy flows. It does not replace test execution, environment setup, or automation scripts; project risk should still drive priorities and data choices.

Use Cases

  • Review a login spec and split normal, error, security, concurrency, and failure flows into an expected-result table.
  • Before launch, add boundary price, stock failure, payment error, and cross-device cases from cart business rules.
  • From a skill design note, build checks for cooldown, damage, combos, and abnormal-state behavior.
  • Before release, verify new content, data migration, localization, and multi-platform behavior coverage.

Best For

  • QA engineers who need to turn requirement docs into reviewable, executable case tables.
  • Engineering leads who must close exception, boundary, and security gaps before handoff.
  • Game designers or system testers checking skill stats, dungeon balance, and gacha rules.
  • Test maintainers inheriting old suites who need coverage backfill and consistent fields.