software_test_case_design

Name: software_test_case_design
Author: cassion-ran

Description

This skill should be used when generating test cases, writing test cases, designing test cases, supplementing exception scenarios and boundary values, design...

README (SKILL.md)

\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

Usage Guidance

This appears to be a purely documentation-driven test-case generation skill — it doesn't request credentials, install code, or call external endpoints. If you plan to use it, consider: 1) whether its built-in templates match your organization's test-case format; 2) avoid feeding sensitive production data into prompts (the skill will generate text based on whatever context you provide); and 3) if you need Excel output, the SKILL.md references using a separate 'xlsx' skill — verify that other skill's permissions before invoking it. Overall it is coherent and proportionate for its stated purpose.

Capability Analysis

Type: OpenClaw Skill Name: software-test-case-design Version: 1.0.2 This skill bundle is a comprehensive documentation set for software test case design across various platforms, including Mobile App, Web, Desktop, and Mini-programs. It consists entirely of Markdown files providing methodologies, checklists, and examples for functional, API, UI, and security testing. There is no executable code, no external network calls, and no instructions that attempt to subvert the AI agent or exfiltrate data. The security testing sections (e.g., in common-testing.md and common-checklist.md) are standard QA guidelines for identifying vulnerabilities in target applications and do not contain malicious payloads or exploit instructions.

Capability Tags

cryptocan-make-purchasesrequires-oauth-tokenrequires-sensitive-credentials

Capability Assessment

✓ Purpose & Capability

Name/description match the provided content: all included files are test-case templates, platform-specific guidance, examples and checklists. The skill does not request unrelated binaries, credentials, or system paths.

✓ Instruction Scope

SKILL.md tells the agent to load local reference documents based on keywords and to generate test-case outputs. It does not instruct reading system files, environment variables, network exfiltration, or executing scripts. The 'progressive disclosure' guideline restricts scope to included docs.

✓ Install Mechanism

No install spec and no code files — the skill is instruction-only, so nothing is written to disk or downloaded at install time.

✓ Credentials

The skill declares no required environment variables, credentials, or config paths. The runtime instructions reference only bundled reference files appropriate to test-case generation.

✓ Persistence & Privilege

always is false and there are no indications the skill modifies other skills or system-wide settings. Autonomous invocation is allowed (platform default) but the skill's scope is limited to local document use and text generation.

Version History

v1.0.2

- Added new command keywords for "test quality", "quality standard", "page interaction", "component interaction", and "animation interaction" to improve command mapping coverage. - Adjusted command mapping for "accessibility testing": now explicitly states dedicated accessibility testing is not included. - Updated example references for "functional testing" to point to a smaller, more precise segment (Lines 20–86) in examples/common.md. - Clarified mapping detail and coverage throughout the command trigger table for better transparency.

v1.0.1

- Major update: Introduced modular file structure and platform-specific content for test case design guidance. - Added comprehensive references, checklists, templates, and example files for various platforms (Mobile App, Mini Program, Mobile Web, PC Web, Desktop). - Streamlined skill description and clarified supported/non-supported capabilities. - Organized command mapping for precise file and section loading based on test scenario keywords. - Updated output structure and loading guidance for easier use and scalability.

v1.0.0

Initial release of senior-level software test case design skill. - Delivers high-quality, enterprise-standard functional test cases with complete field coverage. - Supports complex scenarios including page navigation, route parameters, multi-page linkage, and exception flows. - Outputs fully structured test cases following a strict, standardized template for manual or automated use. - Emphasizes clear logic, deep requirement breakdown, high test coverage, and risk-driven prioritization. - Incorporates advanced test design techniques such as equivalence partitioning, decision tables, and scenario-based methods.

Metadata

Slug software-test-case-design

Version 1.0.2

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 3

Frequently Asked Questions

What is 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... It is an AI Agent Skill for Claude Code / OpenClaw, with 111 downloads so far.

How do I install software_test_case_design?

Run "/install software-test-case-design" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is software_test_case_design free?

Yes, software_test_case_design is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does software_test_case_design support?

software_test_case_design is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created software_test_case_design?

It is built and maintained by Cassion-Ran (@cassion-ran); the current version is v1.0.2.

More Skills