ClawHub

AI Test Case Generator

v1.0.1

Use when turning requirements, screenshots, or other QA inputs into structured test cases and review questions with an AI-assisted workflow.

⭐ 0· 203·0 current·0 all-time
byXuXu@xuxuclassmate

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for xuxuclassmate/ai-testcase-generator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "AI Test Case Generator" (xuxuclassmate/ai-testcase-generator) from ClawHub.
Skill page: https://clawhub.ai/xuxuclassmate/ai-testcase-generator
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ai-testcase-generator

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-testcase-generator
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the content: guidance for converting requirements/screenshots into test cases and review questions. No unrelated capabilities or resources are requested.
✓
Instruction Scope
SKILL.md contains only workflow and output templates for QA/test case generation. It does not instruct reading arbitrary system files, accessing env vars, or transmitting data to external endpoints.
✓
Install Mechanism
No install spec and no code files — the skill is documentation-only, so nothing is written to disk or installed.
✓
Credentials
No environment variables, credentials, or config paths are required. Requested inputs are user-provided content and context only.
✓
Persistence & Privilege
always is false and the skill makes no claims about modifying agent config or persisting credentials. Normal autonomous invocation is allowed by platform defaults but is not required by the skill.
Assessment
This skill is low-risk because it's documentation-only and asks for no credentials or installs. Before using, avoid pasting sensitive secrets into the requirements you provide, and consider whether your platform logs conversation content (so you can protect confidential product details). If you need automated exports (spreadsheets, binary artifacts), note the skill explicitly warns it does not produce those outputs by itself — you'd need a separate generator or tool for that.

Like a lobster shell, security has layers — review code before you run it.

aivk9797ywcn4y3t66jevyt9b7r8d85bcajautomationvk9797ywcn4y3t66jevyt9b7r8d85bcajlatestvk9797ywcn4y3t66jevyt9b7r8d85bcajqavk9797ywcn4y3t66jevyt9b7r8d85bcajreviewvk9797ywcn4y3t66jevyt9b7r8d85bcajtestcasesvk9797ywcn4y3t66jevyt9b7r8d85bcajtestingvk9797ywcn4y3t66jevyt9b7r8d85bcaj
203downloads
0stars
9versions
Updated 6d ago
v1.0.1
MIT-0
XuXu@xuxuclassmate
aiautomationlatestqareviewtestcasestesting
Download

AI Test Case Generator

This ClawHub package is documentation-only. It does not embed runtime binaries, install scripts, or package manifests.

When to use

  • A user wants test cases from a PRD, specification, screenshot, or plain text brief.
  • You need a structured review loop for QA coverage before implementation or release.
  • You want a checklist for turning requirements into executable test work.

Inputs to collect

  • Requirement text or a file path
  • Product stage: requirement review, implementation, or pre-release
  • Preferred output language
  • Any focus area such as security, edge cases, compatibility, or accessibility

Recommended workflow

  1. Extract the core flows. Identify user journeys, rules, dependencies, and constraints.
  2. Group coverage by module. Organize cases by feature area, API, UI surface, or role.
  3. Add negative and edge paths. Include invalid input, permission boundaries, failures, and concurrency where relevant.
  4. Run a review pass. Check coverage, clarity, execution readiness, and security impact.

Recommended outputs

  • Test scope summary
  • Test points grouped by module
  • Detailed cases with steps and expected results
  • Priority or severity labels
  • Open questions for product or engineering

Guardrails

  • Keep uploaded requirements confidential.
  • State clearly when a case depends on missing product detail.
  • Do not claim that spreadsheet, XMind, or binary exports were produced unless an actual generator runtime was used outside this skill bundle.

Comments

Loading comments...