# Generate Game Test Cases

Game teams need reliable test coverage from requirements, prototypes, and spreadsheets. This skill turns those inputs into structured Markdown, Excel-ready, or Xmind-ready test cases.

## Install

```bash
npx skillstore add snake-mustang/game-test-case-generator
```

## Metadata

- Status: approved
- Slug: snake-mustang-game-test-case-generator
- Skillstore revision: r1
- Version status: missing
- Tree hash: 6261f8fa8bc62bae89a94178f0a13c7d2038b6962ba71e731a33a78d09c84ec7
- Author: snake-mustang
- GitHub username: snake-mustang
- License: MIT
- Repository: https://github.com/snake-mustang/sy-testcase-generator/tree/main/
- Ref: f93e9bb0daca99badb6a7e574b97737155d57cb3
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/snake-mustang-game-test-case-generator
- Manifest: https://skillstore.pages.dev/api/skills/snake-mustang-game-test-case-generator/manifest

## Capabilities

- Builds a requirement mapping table from game requirement materials.
- Generates full test cases with IDs, priorities, preconditions, steps, expected results, and exception branches.
- Generates quick checklist-style test points for fast review.
- Covers normal, boundary, exception, performance, security, compatibility, and UI scenarios.
- Marks unclear or conflicting requirements with suggested options.
- Provides local scripts to convert Markdown output into Excel or Xmind-compatible Markdown.

## Use Cases

- Create QA Coverage From Requirements: Convert a game feature document into executable test cases with priorities and expected results.
- Review Feature Gaps Before Development: Identify unclear rules, missing values, and conflicting prototype details before implementation starts.
- Prepare Fast Regression Checklists: Generate concise test points for login, events, rewards, UI, and compatibility reviews.

## Prompt Templates

### Create a Quick Checklist

```
Use quick mode to create test points for this game feature: [paste feature description]. Include core, boundary, exception, performance, security, compatibility, and UI sections. Mark unclear requirements.
```

### Generate Full Test Cases

```
Use full mode for the attached requirements. Produce case IDs, module names, test type, priority, preconditions, operation steps, expected results, exception branches, and pending questions.
```

### Convert Spreadsheet Requirements

```
Read the uploaded CSV or XLSX requirements. Build a requirement mapping table, then generate full game test cases with coverage statistics and questions for missing details.
```

### Audit Complex Event Coverage

```
Review these event requirements and prototype notes. Identify missing or conflicting rules, generate parameterized test cases, and prepare Markdown that can be converted to Excel and Xmind.
```

## Limitations

- It does not validate cases against a running game build or live service.
- Prototype image interpretation depends on the vision support of the host AI model.
- Excel and Xmind conversion require local Python dependencies and well-formed Markdown input.
- Generated cases still need QA and product review for business rules and reward values.

## Best Practices

- Provide module names, acceptance criteria, data ranges, and known edge cases with each request.
- Use quick mode for early review and full mode when cases will be executed by testers.
- Resolve pending questions with product owners before importing cases into a test management system.

## Anti Patterns

- Do not treat generated cases as final without QA review.
- Do not ask the skill to invent business-critical probabilities or reward values without source requirements.
- Do not run conversion scripts on untrusted Markdown without checking the input and output paths.

## Security Audit

- Audited at: 2026-07-07T06:11:12.709\+00:00
- Summary: Manual review found that the static alerts are false positives caused by Markdown examples, normal documentation, and local conversion utilities. No evidence found of prompt injection, unauthorized networking, hidden data access, obfuscated payloads, or malicious intent.

## Stats

- Views: 279
- Downloads: 32
- Favorites: 1
- Popularity score: 0