Skip to content

rampstackco/claude-skills / skills/test-case-authoring

test-case-authoring

Verified

Write 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.

references/exploratory-charter-template.md

View on GitHub
# Exploratory Charter Template

A charter points a timeboxed session at a question. It is the right tool when the answer is not known well enough to script cases: a spike, a new integration, a story with real unknowns, or a bug with no repro.

Findings are notes, not pass/fail.

---

## Charter

```
CHARTER ID: [EX-01]
TICKET: [ticket ID and title]
TIMEBOX: [30 / 60 / 90 minutes]
TESTER: [name, or agent]

EXPLORE: [target area, e.g., "the import flow with files from other tools"]
WITH: [resources, e.g., "five sample files of different sizes and encodings"]
TO DISCOVER: [the question, e.g., "where does the import fail, and does it tell the user why?"]

SETUP
- Environment: [where]
- Data: [what is loaded]
- Flags: [states]
```

The one-line form is: **Explore** [target] **with** [resources] **to discover** [question].

---

## Session notes

```
SESSION: [EX-01], [date], [start time] to [end time]

WHAT I TRIED
- [Action and input]
- [Action and input]

WHAT I SAW
- [Observation, with screenshot or log reference]
- [Observation]

SURPRISES
- [Anything unexpected, even if not a bug]

BUGS FILED
- [ticket ID and title, or none]

QUESTIONS RAISED
- [Question for the PM, designer, or engineer]

NEW SCRIPTED CASES TO WRITE
- [Case title and trace]

COVERAGE
- Explored: [what the session covered]
- Not explored: [what was left, and whether it needs another charter]

TIME SPLIT (rough)
- Setup: [n] min / Testing: [n] min / Investigating bugs: [n] min
```

---

## Charter rules

- **One question per charter.** Two questions means two charters.
- **Stop at the timebox.** If the question is not answered, write what is still unknown and propose the next charter.
- **Record as you go.** Notes written after the session lose the detail that made the bug reproducible.
- **File bugs with repro steps.** A finding that is a bug becomes a bug ticket with `ticket-authoring`.
- **Turn knowns into cases.** Once a behavior is understood, write a scripted case so it is checked every release.

---

## Example charters

| Explore | With | To discover |
|---|---|---|
| The CSV import | Files exported from three other tools, one with a byte-order mark | Which files fail and whether the error names the problem |
| Checkout on a slow network | Network throttled to a slow mobile profile | Whether double-tapping Pay can create two orders |
| A candidate messaging provider's sandbox | The provider's test numbers and opt-out keywords | Whether opt-out replies reach our webhook within a minute |
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall