casely
Generate test cases from documentation automatically
Casely eliminates 40% of QA engineering time by converting requirement documents into structured test cases. It learns your team's writing style from examples and exports TestRail-ready Excel files.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "casely". /init ShoppingCart /parse /style /plan /generate functional CheckoutFlow /export
Expected outcome:
Creates project structure, parses documents, generates style guide, creates test plan with 45 estimated cases, generates functional test cases for checkout flow, and exports to Excel files in exports/ folder.
Using "casely". Generate negative test cases for the payment processing module based on the requirements and style guide.
Expected outcome:
Creates individual Markdown files for each negative test scenario (invalid card numbers, expired cards, declined transactions, etc.) matching the exact column structure from analyzed examples.
Security Audit
SafeAll 123 static analysis findings are false positives. The 'external_commands' patterns are markdown code blocks in documentation showing example bash commands, not actual shell execution. The 'blocker' and 'weak cryptography' findings are from imported libraries (docling, openpyxl) used for document parsing and Excel generation. The skill code itself contains no security vulnerabilities, malicious intent, or dangerous patterns. This is a legitimate QA automation tool.
Quality Score
What You Can Build
New feature test coverage
QA engineers receive a 50-page requirements document for a new payments feature. Casely parses the document, analyzes existing test case examples, and generates 200+ atomic test cases matching the team's format.
Test case migration to TMS
A team has hundreds of test cases in various document formats. Casely converts them all to Markdown, applies consistent formatting, and exports to Excel for import into TestRail or other test management systems.
Rapid test plan creation
During sprint planning, a QA analyst needs to estimate testing effort. Casely scans requirements, identifies modules, and generates a comprehensive test plan with coverage tiers (smoke, critical, full) and case estimates.
Try These Prompts
/init LoginFeature
/parse
/style
/generate functional UserAuthentication
Best Practices
- Always run /parse after uploading new requirement documents to ensure latest content is processed
- Review and edit the generated test_style_guide.md before running /generate to ensure accurate formatting
- Use /plan first to understand scope and estimate test coverage before generating full test suites
- Run /export immediately after /generate to convert Markdown files to Excel for TMS import
Avoid
- Do not skip the /style step as it ensures generated test cases match your team's exact format
- Do not mix test types in a single generation command - use separate /generate calls for each type
- Do not edit generated test case Markdown files directly - regenerate with updated style guide instead
- Do not run /export before completing all /generate operations for consistency