What makes software_test_case_design notable?

1.4K downloads. Trust evidence available

How should software_test_case_design be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

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...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.4k

Updated

Oct 10, 2026

Version

1.0.7

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.4K downloadsadoption · observed Oct 10, 2026
Latest release: 1.0.7release · observed Jun 12, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s1765jzj8wrw7nvtkfg1zwyc1983qbrh:software-test-case-design

Install using `clawhub skill install s1765jzj8wrw7nvtkfg1zwyc1983qbrh:software-test-case-design` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/cassianran/software-test-case-design before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-cassianran-software-test-case-design/snapshot"

Documentation

CLAWHUB

151,981 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: test-case-design
description: This skill should be used when generating test cases, writing test cases, designing test cases, supplementing exception scenarios and boundary values, designing complex interaction test cases, or outputting standardized test cases for specific scenarios or features, such as: functional testing, compatibility testing, adaptation testing, API testing, UI visual testing, mobile/App/mini-program/H5/desktop/PC Web testing, AI Agent testing, linkage testing, or routing testing. It only focuses on writing test cases and does not involve test plans, test strategies, or automation scripts.
---

## Execution Flow

1. **Identify Test Case Type**:
   - Contains "API testing" → API test cases
   - Contains "AI agent testing"/"Agent testing"/"Agent"/"intelligent agent" → Agent test cases
   - Default → Functional test cases
2. **Load Capability Files**: Always load `references/templates/common-rules.md` (rules); select capability files by type:
   - API testing → `references/core-capabilities/api-testing.md`
   - Agent testing → `references/core-capabilities/agent-testing.md` + Part 1: Test Case Design Methods and Part 2: Test Case Quality Standards from `references/core-capabilities/functional-testing.md`
   - Functional testing → `references/core-capabilities/functional-testing.md`
3. **Load Platform-Specific Files** (skip for API testing):
   - Match platform keywords → load `references/platform/{platform}.md`
4. **Generate Test Cases**: Generate test cases according to the loaded capability files and platform-specific files
5. **Self-Check**:
   - API testing → `references/checklists/api-checklist.md`
   - Agent testing → `references/checklists/agent-checklist.md` + Section I: Functional Testing Checklist from `references/checklists/common-checklist.md`
   - Agent testing + platform → `references/checklists/agent-checklist.md` + Section I: Functional Testing Checklist from `references/checklists/common-checklist.md` + `references/checklists/{platform}-checklist.md`
   - Functional testing + platform → `references/checklists/common-checklist.md` + `references/checklists/{platform}-checklist.md`
   - Functional testing without platform → `references/checklists/common-checklist.md`
6. **Output**: Output in Markdown table format as specified in `references/examples/format-spec.md`

## Capability Boundaries
✅ Can generate: Functional testing, API testing, AI Agent testing (including Agent security & boundaries), platform-specific testing
❌ Cannot generate: Test plans, test strategies, test planning documents, penetration testing execution, vulnerability scanning, performance/stress testing (concurrency/stress/load), automation scripts

## Instruction Mapping Table

> The rules file `references/templates/common-rules.md` is always loaded. Capability files are selected by test case type; platform files are overlaid as needed.

### Capability Files

| Keyword Trigger | Load | Description |
|-----------|------|------|
| "API

_meta.json

{
  "ownerId": "kn782h4g39n2ya2vse0rpj6qh183pzwe",
  "slug": "software-test-case-design",
  "version": "1.0.7",
  "publishedAt": 1781230487592
}

references/checklists/agent-checklist.md

# AI Agent Test Case Design Checklist

> This checklist covers six major Agent-specific testing dimensions for self-review and gap identification during test case design.

---

## 0. Test Case Executability Check (common to all test types)

- [ ] Do test steps provide the complete verbatim text of instructions sent to the Agent (rather than descriptive language)?
- [ ] Are there any unqualified descriptions such as "send malicious instruction" or "input abnormal prompt"?
- [ ] Can test inputs be copied and executed directly without the tester having to invent anything?

---

## I. Task Completion

- [ ] Can explicit instructions be accurately understood and executed?
- [ ] Can implicit requirements be inferred and responded to?
- [ ] Can ambiguous requirements be reasonably clarified, or executed per the most likely intent?
- [ ] Does the Agent follow intent drift during multi-turn conversations?
- [ ] Are multi-step tasks executed in the correct order and in full?
- [ ] Is there a degradation/fallback plan when a task partially fails?
- [ ] When a task exceeds capabilities, is it explicitly declined rather than forcibly executed?
- [ ] After task completion, does the result match user expectations?
- [ ] Are intermediate status updates provided for long-running tasks?

## II. Tools & Memory

- [ ] Is the correct tool selected to execute the task?
- [ ] Are tool call parameters correct and complete?
- [ ] Is the tool called at the right moment (not too early, not too late)?
- [ ] Are there redundant or duplicate tool calls?
- [ ] When a tool returns an error, is there retry/degradation/user notification?
- [ ] Are dependency relationships correct in multi-tool sequential calls?
- [ ] Are there conflicts during parallel multi-tool calls?
- [ ] Is memory/history files consulted when needed?
- [ ] Are important decisions and results written to memory?
- [ ] Is the content written to memory accurate and unambiguous?
- [ ] Is memory consistent across multiple sessions?
- [ ] Is early key information retained during long conversations?

## III. Security & Boundaries

- [ ] Are operations beyond role permissions executed?
- [ ] Are malicious instructions in user input properly isolated?
- [ ] Is sensitive information (keys/passwords/internal configuration) leaked?
- [ ] Is the role setting hijacked by user prompts?
- [ ] Are harmful/illegal requests properly declined?
- [ ] Is there risk of infinite loops or resource waste?
- [ ] Is session information isolated between different users?
- [ ] Are high-risk operations (delete/send/payment) confirmed?
- [ ] Are file operations within safe scope?
- [ ] Do network requests access unauthorized addresses?
- [ ] Is there fault tolerance for extreme inputs (empty input, extremely long input, special characters)?
- [ ] Is there fault tolerance for system exceptions (server errors, network timeouts, tool unavailability)?
- [ ] Is there graceful degradation rather than crash when resources are exhausted?

## IV. Pe

references/checklists/api-checklist.md

# API Testing Checklist

> This checklist covers all dimensions of API testing for item-by-item self-review after API test case design.

---

## Table of Contents

| Line | Section |
|------|---------|
| 13 | 0. Test Case Executability Check |
| 20 | I. Functional Testing |
| 28 | II. Data Validation |
| 36 | III. Authentication & Authorization |
| 43 | IV. Error Handling |
| 50 | V. Pagination & Sorting |
| 56 | VI. Search & Filtering |
| 62 | VII. Version Management |
| 68 | VIII. API Documentation |

---

## 0. Test Case Executability Check (common to all test types)

- [ ] Do test steps provide concrete parameter values/request bodies/path values (rather than descriptive language)?
- [ ] Are there any unqualified descriptions such as "send a request with invalid parameters" or "input abnormal data"?
- [ ] Do request parameters specify concrete key=value pairs?
- [ ] For large data scenarios (e.g., oversized request bodies, extremely long string parameters), is descriptive language with explicit parameter specifications used?

---

## I. Functional Testing

- [ ] GET request returns normally
- [ ] POST creates resource successfully
- [ ] PUT/PATCH updates successfully
- [ ] DELETE deletes successfully
- [ ] Batch operations correct
- [ ] Status codes conform to specification
- [ ] Error responses are clear

---

## II. Data Validation

- [ ] Required field validation
- [ ] Field type validation
- [ ] Field format validation
- [ ] Field length validation
- [ ] Field range validation
- [ ] Uniqueness validation
- [ ] Business rule validation

---

## III. Authentication & Authorization

- [ ] Token authentication works correctly
- [ ] Unauthenticated access is rejected
- [ ] Unauthorized access is rejected
- [ ] Token expiry is handled
- [ ] Token refresh works correctly
- [ ] Permission isolation is correct

---

## IV. Error Handling

- [ ] Error codes follow specification
- [ ] Error messages are clear
- [ ] Exceptions are caught
- [ ] Logging is in place
- [ ] Retry mechanism exists
- [ ] Idempotency is guaranteed

---

## V. Pagination & Sorting

- [ ] Pagination parameters work correctly
- [ ] Total count is correct
- [ ] Sorting functionality works correctly
- [ ] Default sorting is reasonable

---

## VI. Search & Filtering

- [ ] Exact search works correctly
- [ ] Fuzzy search works correctly
- [ ] Multi-condition combination is correct
- [ ] Filtering functionality works correctly

---

## VII. Version Management

- [ ] Version control is correct
- [ ] Backward compatibility is maintained
- [ ] Version documentation is complete

---

## VIII. API Documentation

- [ ] Conforms to Swagger/OpenAPI specification
- [ ] Parameter descriptions are complete
- [ ] Examples are clear
- [ ] Error code documentation is provided

references/checklists/common-checklist.md

# General Testing Checklist

This document consolidates checklists for functional testing, linkage testing, routing testing, and UI visual testing. See `checklists/api-checklist.md` for API testing checklist.

## Table of Contents

| Line | Section |
|------|---------|
| 17 | 0. Test Case Executability Check |
| 25 | I. Functional Testing Checklist |
| 71 | II. Linkage Testing Checklist |
| 116 | III. Routing Testing Checklist |
| 167 | IV. UI Visual Testing Checklist |

---

## 0. Test Case Executability Check (common to all test types)

- [ ] Do test steps provide concrete input values/parameters/operation targets (rather than descriptive language)?
- [ ] Are there any unqualified descriptions such as "enter an excessively long string," "enter special characters," "enter test attack vector," or "fill in form required fields"?
- [ ] For large data input scenarios (e.g., 10,000-character text, 500MB file), is descriptive language with explicit parameter specifications used?

---

## I. Functional Testing Checklist

### Test Coverage
- [ ] All function points are covered
- [ ] Normal flows are covered
- [ ] Exception flows are covered
- [ ] Boundary conditions are covered
- [ ] Special scenarios are covered

### Functional Correctness
- [ ] Functions are implemented per requirements
- [ ] Business logic is correct
- [ ] Data processing is correct
- [ ] State transitions are correct
- [ ] Permission control is correct

### Input Validation
- [ ] Valid input is handled correctly
- [ ] Invalid input provides friendly prompts
- [ ] Boundary values are handled correctly
- [ ] Special characters are handled correctly
- [ ] Null values are handled correctly

### Output Validation
- [ ] Displayed content is correct
- [ ] Data format is correct
- [ ] Sorting is correct
- [ ] Filtering is correct
- [ ] Statistics are correct

### Interaction Testing
- [ ] User operation flow is smooth
- [ ] Page navigation is correct
- [ ] Button functionality is correct
- [ ] Form submission is correct
- [ ] List operations are correct

### Data Consistency
- [ ] Frontend-backend data is consistent
- [ ] Multi-platform data is consistent
- [ ] Cache and database are consistent
- [ ] History records are correct
- [ ] Real-time data is correct

---

## II. Linkage Testing Checklist

### Form Linkage
- [ ] Province/city/district cascading
- [ ] Category selection linkage
- [ ] Conditional show/hide
- [ ] Data cascading
- [ ] Form validation linkage
- [ ] Submit button state linkage

### List Linkage
- [ ] Master-detail list linkage
- [ ] Filter condition linkage
- [ ] Sort linkage
- [ ] Pagination linkage
- [ ] Selection state linkage

### Search Linkage
- [ ] Search keyword suggestions
- [ ] Search result linkage
- [ ] Search history linkage
- [ ] Trending search linkage

### State Linkage
- [ ] Button state linkage
- [ ] Menu state linkage
- [ ] Tab state linkage
- [ ] Icon state linkage
- [ ] Color state linkage

### Data Linkage
- [ ] Real-time data synchronization
- [ ]

Github ReposUpdated 21h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.