software_test_case_design
/install software-test-case-design
\r \r
Loading Guide\r
\r
Progressive Disclosure Principle: Read SKILL.md first to get the full picture, then load corresponding references files based on scenario keywords. No need to load all at once.\r \r
Design Sequence\r
\r Function (Positive + Boundary + Exception) → API → Security → Platform Specific\r \r
Output\r
\r
- Default Markdown table, use xlsx Skill for Excel output\r
- No platform specified → General test cases only; Platform specified → General + Platform specific\r
- Structure: ID | Title | Type | Module | Priority | Preconditions | Steps | Expected Results\r \r
Capability Boundaries\r
✅ Can generate: Functional testing, boundary values, exception scenarios, API testing, security awareness, UI visual test cases, performance experience test cases (response time, loading speed)\r ❌ Cannot generate: Test plans, test strategies, test plans, penetration test execution, vulnerability scanning, performance stress testing (concurrency, stress, load testing), automation scripts\r \r
Command Mapping Table\r
\r
| Keyword Trigger | Load File | Precise Positioning |\r
|-----------|---------|---------|\r
| "test case", "write test case", "design test case" (general) | references/core-capabilities/common-testing.md + references/templates/common-rules.md | common-testing.md full load |\r
| "mobile testing", "App testing" | references/core-capabilities/common-testing.md + references/platform/mobile-app.md + references/templates/common-rules.md | platform/mobile-app.md: specific test points |\r
| "mini program testing" | references/core-capabilities/common-testing.md + references/platform/mini-program.md + references/templates/common-rules.md | platform/mini-program.md: specific test points |\r
| "mobile Web testing", "H5 testing" | references/core-capabilities/common-testing.md + references/platform/mobile-web.md + references/templates/common-rules.md | platform/mobile-web.md: specific test points |\r
| "desktop testing", "desktop app testing" | references/core-capabilities/common-testing.md + references/platform/desktop.md + references/templates/common-rules.md | platform/desktop.md: specific test points |\r
| "PC Web testing", "Web testing" | references/core-capabilities/common-testing.md + references/platform/pc-web.md + references/templates/common-rules.md | platform/pc-web.md: specific test points |\r
| "linkage testing" | references/core-capabilities/common-testing.md | Lines 116-159: Part 3 Linkage Testing |\r
| "routing testing", "navigation testing" | references/core-capabilities/common-testing.md | Lines 160-214: Part 4 Routing Testing |\r
| "UI testing", "visual testing", "interface testing" | references/core-capabilities/common-testing.md | Lines 215-300: Part 5 UI Visual Testing |\r
| "API testing", "API testing" | references/core-capabilities/common-testing.md | Lines 301-375: Part 6 API Testing |\r
| "security testing" | references/core-capabilities/common-testing.md | Lines 376-443: Part 7 Security Testing |\r
| "boundary value", "exception scenario" | references/core-capabilities/common-testing.md | Lines 22-86: Part 1 Test Case Design Methods |\r
| "test quality", "quality standard" | references/core-capabilities/common-testing.md | Lines 87-115: Part 2 Test Case Quality Standards |\r
| "page interaction", "component interaction", "animation interaction" | references/core-capabilities/common-testing.md | Lines 444-549: Part 8-10 Interaction Testing |\r
| "compatibility testing", "adaptation testing" | references/core-capabilities/common-testing.md | Load corresponding platform/ file by platform |\r
| "accessibility testing" | references/platform/mobile-app.md | Section 6: Device Compatibility — Note: this skill does NOT include dedicated accessibility testing content; only device/screen/resolution compatibility is covered here. Accessibility testing (contrast, screen reader, focus management) is not yet documented in this skill. |\r
| "functional testing" | references/core-capabilities/common-testing.md + references/templates/common-rules.md + references/examples/common.md | examples/common.md Lines 20-86: Part 1 Functional Testing |\r
| Checklist (General) | references/checklists/common-checklist.md | |\r
| Checklist (Platform Specific) | references/checklists/mobile-app-checklist.md / mobile-web-checklist.md / pc-web-checklist.md / desktop-checklist.md / mini-program-checklist.md | |\r
| Example Reference | references/examples/common.md + references/examples/{platform}.md | examples/common.md contains table of contents |\r
\r
File Structure\r
\r
Note: This skill has no scripts/ or assets/ directories, all content is provided through references/.\r \r
references/\r
├── templates/ # Template rules\r
│ └── common-rules.md # Test case template + test types + priority + numbering\r
├── core-capabilities/ # General testing capabilities\r
│ └── common-testing.md # All general testing capabilities (with TOC)\r
├── platform/ # Platform specific test points\r
│ ├── mobile-app.md # Mobile App: gestures/interruption/network/permissions/push/compatibility/performance\r
│ ├── mobile-web.md # Mobile Web: responsive/touch/browser/viewport/login payment/H5/SEO\r
│ ├── pc-web.md # PC Web: browser/layout/keyboard/forms/session/multi-window/routing/linkage/drag/richtext/i18n/dark/print\r
│ ├── desktop.md # Desktop: window/shortcuts/files/system integration/multi-monitor/install update/compatibility\r
│ └── mini-program.md # Mini Program: lifecycle/authorization/sharing/payment/navigation/subscription/platform differences\r
├── checklists/ # Test case design checklists\r
│ ├── common-checklist.md # General checklist (with TOC)\r
│ ├── mobile-app-checklist.md\r
│ ├── mobile-web-checklist.md\r
│ ├── pc-web-checklist.md\r
│ ├── desktop-checklist.md\r
│ └── mini-program-checklist.md\r
└── examples/ # Example references\r
├── common.md # General test examples (with TOC)\r
├── mobile-app.md # Mobile App examples\r
├── mobile-web.md # Mobile Web examples\r
├── pc-web.md # PC Web examples\r
├── desktop.md # Desktop examples\r
└── mini-program.md # Mini Program examples\r
```\r
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install software-test-case-design - 安装完成后,直接呼叫该 Skill 的名称或使用
/software-test-case-design触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
software_test_case_design 是什么?
This skill should be used when generating test cases, writing test cases, designing test cases, supplementing exception scenarios and boundary values, design... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 111 次。
如何安装 software_test_case_design?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install software-test-case-design」即可一键安装,无需额外配置。
software_test_case_design 是免费的吗?
是的,software_test_case_design 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
software_test_case_design 支持哪些平台?
software_test_case_design 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 software_test_case_design?
由 Cassion-Ran(@cassion-ran)开发并维护,当前版本 v1.0.2。