test-case-generator
Skill4 starsChanged 27 days agoMITView on GitHub
Use when QA or developers need manual test cases or test scenarios from a requirement, user story, PRD, ticket, acceptance criteria, UI screen or feature description, including negative, boundary and edge cases, in a table or test-management format.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- xmh-test/test-agent-skillstheir own version, first seen May 25, 2026
- ShreyasBh02/AI-Skills-Collectiontheir own version, first seen Mar 30, 2026
- aryankumar06/claude-code-skillstheir own version, first seen Mar 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aryankumar06/claude-code-skills★ 16same name
- xmh-test/test-agent-skills★ 5same name
- ShreyasBh02/AI-Skills-Collection★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- accessibility-auditSkill
- api-design-reviewSkill
- api-test-writerSkill
- architecture-diagramSkill
- bug-debuggerSkill
- bug-report-writerSkill
- changelog-writerSkill
- codebase-onboardingSkill
- code-reviewSkill
- database-schema-designSkill
- dependency-upgradeSkill
- design-handoff-specSkill
- design-reviewSkill
- dockerize-appSkill
- figma-design-compareSkill
- flaky-test-fixerSkill
- git-commit-writerSkill
- github-actions-ciSkill
- playwright-e2e-testsSkill
- prd-writerSkill
- proof-of-done-liteSkill
- readme-writerSkill
- refactor-plannerSkill
- security-auditSkill
- seo-auditSkill
- test-plan-writerSkill
- test-writerSkill
- ux-research-synthesisSkill
- ux-writingSkill
- web-performance-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
If the user's team uses a specific tool (TestRail, Zephyr, Xray, Excel), match its columns.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Case Generator
Overview
Turn a requirement into test cases that a tester can run without asking questions, and that would catch the bugs most likely to ship. Cover the happy path once and spend most cases on boundaries, errors and states.
Method
- Extract testable rules from the input: inputs and their valid ranges, business rules, roles and permissions, states and transitions, integrations, messages shown to users. List ambiguities as questions instead of guessing.
- Apply design techniques to each rule:
| Technique | Use for |
| Equivalence partitioning | One case per class of valid and invalid input |
| Boundary values | min-1, min, min+1, max-1, max, max+1, empty, very long |
| Decision table | Rules that combine conditions (role × plan × status) |
| State transition | Workflows: allowed and forbidden moves between states |
| Error guessing | Duplicates, special characters, emoji, leading/trailing spaces, time zones, double submit, back button, slow network, session expiry |
- Add non-functional checks relevant to the feature: permissions, accessibility basics, responsive layouts, performance with large data, localization.
- Write the cases in the format below. One expected result per case, observable and specific.
- Prioritize: P1 for the core flow and anything touching money, data loss or security; P2 for common variations; P3 for rare edge cases.
Output format
| ID | Title | Priority | Type | Preconditions | Steps | Test data | Expected result |
| TC-01 | Apply valid coupon at checkout | P1 | Positive | Logged-in user, cart total ₹1,000 | 1. Open cart 2. Enter coupon 3. Click Apply | SAVE10 | Total shows ₹900; message "Coupon applied" |
Type is one of: Positive, Negative, Boundary, Permission, State, UI, Non-functional.
Then Coverage summary (rules → case IDs) and Open questions for the product owner.
If the user's team uses a specific tool (TestRail, Zephyr, Xray, Excel), match its columns; for BDD teams write scenarios in Gherkin (Given / When / Then).
Common mistakes
- Ten positive cases and no negative ones.
- Expected results like "works correctly" or "page loads".
- Steps that depend on knowledge only the writer has.
- Combining several checks in one case, so a failure does not show what broke.
- Guessing business rules instead of listing them as open questions.
Made by Wageesha Tripathi · LinkedIn · Email · More skills
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.