Use Case Testing

Derive test scenarios from use case specifications to validate end-to-end user workflows including main success, alternate, and exception paths. Use for acceptance testing and requirements validation.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill use-case-testing
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/qa-engineer/functional-testing/skills/use-case-testing ~/.claude/skills/use-case-testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Use Case Testing

Derive comprehensive test scenarios from use case specifications, ensuring every main success path, alternate flow, and exception path is exercised end-to-end as a real user would experience it.

## Context

You are a senior QA engineer designing use case tests for $ARGUMENTS. This technique bridges requirements and testing, validating that the system fulfills its intended purpose from the user's perspective.

## Domain Context

- **ISTQB Foundation Syllabus (4.2.5)**: Use case testing is a black-box technique that derives tests from use case descriptions, covering main and alternative scenarios
- **Alistair Cockburn's _Writing Effective Use Cases_**: Defines the standard use case template — actor, preconditions, main success scenario, extensions (alternate/exception paths), postconditions, and guarantees
- **ISO/IEC 25010**: Functional appropriateness measures whether functions facilitate task completion — use case testing directly validates this
- **Requirements traceability** (IEEE 830): Each test case should trace back to a specific use case step, providing bidirectional coverage evidence

## Instructions

1. **Enumerate use cases**: List all use cases for the feature under test. For each, identify the primary actor, preconditions, trigger, and postconditions. If formal use cases don't exist, derive them from user stories, PRDs, or stakeholder interviews
Read the full skill on GitHub

Details

Skill name
use-case-testing
Path
qa-engineer/functional-testing/skills/use-case-testing/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Use Case Testing skill do?

Derive test scenarios from use case specifications to validate end-to-end user workflows including main success, alternate, and exception paths. Use for acceptance testing and requirements validation.

How do I install the Use Case Testing skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Use Case Testing popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.