rampstackco/claude-skills / skills/test-case-authoring
test-case-authoring
VerifiedWrite the test plan and test cases for a single work item: every acceptance criterion traced to a case, each case with test data, steps, an observable expected result, a level, and the evidence a pass must leave behind. Use this skill whenever the user wants to write test cases, a test plan, or QA notes for a ticket, plan regression tests for a bug fix, build a traceability matrix, choose between unit, integration, end-to-end, and manual tests, or charter exploratory testing for a spike. Triggers on test cases, test plan, QA notes, how do I test this, write tests for this ticket, acceptance test, regression test, traceability, test coverage for a story, exploratory testing, test charter, what should QA check, fix verification. Also triggers when the user pastes a ticket or a set of acceptance criteria and asks whether it is testable, even if they never say test plan.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 360 B |
| SKILL.md | skill md | 11.4 KB |
| references/coverage-checklist.md | markdown | 3.0 KB |
| references/example-test-plan-story.md | markdown | 7.9 KB |
| references/exploratory-charter-template.md | markdown | 2.4 KB |
| references/test-case-template.md | markdown | 3.1 KB |
| references/test-plan-template.md | markdown | 2.9 KB |
| references/traceability-matrix-template.md | markdown | 2.7 KB |
references/test-plan-template.md
View on GitHub# Test Plan Template
One plan per work item. It is short: the cases carry the detail. The plan says what is in scope, which classes are covered, where it runs, and what evidence comes back.
The summary section goes into the ticket's QA notes. The rest attaches to the ticket or lives next to it.
---
## Template
```
TEST PLAN: [ticket ID and title]
TICKET TYPE: [bug / task / story / spike]
AUTHOR: [name]
DATE: [yyyy-mm-dd]
SPEC: [link, or none]
SCOPE
In scope:
- [Acceptance criteria AC-1 to AC-n, or the repro and QA notes]
- [Named risks: what else shares the code path]
Out of scope:
- [What this plan does not test, and where it is covered instead]
COVERAGE CLASSES
| Class | Covered | Cases | If not covered, why |
|---|---|---|---|
| Happy path | yes / no | TC-.. | |
| Boundary and edge | yes / no | TC-.. | |
| Negative and error | yes / no | TC-.. | |
| Regression | yes / no | TC-.. | |
| Accessibility smoke | yes / no | TC-.. | |
| Performance smoke | yes / no | TC-.. | |
LEVELS
| Level | Cases | Notes |
|---|---|---|
| Unit | TC-.. | |
| Integration | TC-.. | |
| End-to-end | TC-.. | |
| Manual | TC-.. | Reason each is manual |
ENVIRONMENTS
- [Environment]: [what runs there, data fixtures, flag states]
EVIDENCE TO ATTACH
- [Per case or per group: runner summary, screenshot, log line, recording]
ENTRY CRITERIA
- [What must be true before testing starts: build deployed, fixtures loaded, flag on]
EXIT CRITERIA
- [What must be true to call the item verified: all cases pass, or failures filed and accepted]
UNTESTABLE OR DEFERRED
- [Case or criterion, reason, what would make it testable, owner]
QA NOTES SUMMARY (paste into the ticket)
[Three to six lines: classes covered, case count by level, environments, where the evidence will be posted, anything untestable.]
```
---
## Filling the plan by ticket type
| Type | Minimum content |
|---|---|
| Bug | Failing case (the repro as a test), regression cases for every shared path, fix verification case named on the ticket |
| Story | Every criterion traced, all six classes considered, levels chosen per case |
| Task | Happy path and regression, mapped to the definition of done and the touches list |
| Spike | Exploratory charters in place of cases; exit criteria are the spike's own |
---
## Entry and exit criteria
Entry criteria stop wasted test runs. If the fixture data is not loaded, every case fails for the wrong reason.
Exit criteria stop endless testing. "All cases pass" is one valid exit. "All cases pass except TC-07, filed as a separate bug and accepted by the PM as not blocking" is another, if it is written down.
---
## Untestable or deferred
Some criteria cannot be tested before release: a metric that needs a month of data, a third-party behavior with no sandbox, a load level the staging environment cannot produce. List them here with the reason and what would make them testable. An untestable criterion hidden inside a passing plan is worse than one named in the open.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |