Claude Code use-case-tests for traceable acceptance tests
Organize tests by main flow, alternative flow, and business rules so failures can be traced back to a use-case specification.
中文Install in Claude Code
Open Spec-Driven Development Template in Claude Code. Choose the Java, Maven and Vaadin test approach where applicable. Hilla frontend flows also use Vitest.
- Review `.claude/skills/use-case-tests/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/use-case-tests/` in your project and save the reviewed file as `.claude/skills/use-case-tests/SKILL.md`.
- Start Claude Code from that project's root, then select `/use-case-tests` in the slash menu.
Example task
Specification UC-17 covers library catalog search. The main flow returns 2 rows for “Atlas records”. AF-1 returns 0 rows and the “No results” label for “Moon marble”.What to check
Tests map to Main Flow and AF-1, with {matchedCount: 2, emptyCount: 0, emptyLabel: 'No results'} and method names tied to the specified flows.
Original SKILL.md on GitHub · Updated
Frequently asked question
Where do I group tests covering both the frontend and services?
Keep tests traceable to the same use case together, then use a suitable mechanism for each individual behavior.