uc-test-designer

Generates use-case-based test cases and bug reports for EShop functional requirements.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill uc-test-designer-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uc-test-designer
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.claude/skills/uc-test-designer
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill uc-test-designer-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing black-box test cases from a requirements specification is slow and inconsistent when done by hand. This Skill turns EShop functional requirements (FR-01 to FR-24) into a complete Use-Case Testing artifact set: use case documents, test design analysis, detailed test cases, bug reports, and a traceability matrix. ## Core Features & Use Cases - Use Case Modeling: Produces use cases in the Flow of Events format (Title, Primary Actor, Level, Preconditions, Guarantees, Main Success Scenario, Extensions) grounded in the README specification. - Test Case Generation: Creates one markdown test case for the main success scenario plus one per extension, following a fixed TC template with preconditions, test data, steps, and expected results. - Execution & Bug Reporting: Supports running tests against the live system and writing one bug report file per failure, plus a traceability matrix linking scenarios, requirements, test cases, and bugs. - Use Case: Ask it to apply use-case testing to FR-08 (checkout); it suggests applicable FRs, drafts the use case, waits for your confirmation at each step, then generates the full test suite folder structure. ## Quick Start Ask the agent to do use case testing for FR-08 checkout and confirm each step as it proposes the use case, test cases, and execution plan.

Frequently Asked Questions about uc-test-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design test cases using use case testing?▼

Write the use case in Flow of Events format with a Main Success Scenario and numbered Extensions, then derive one test case for the main flow and one for each extension. This Skill automates that derivation from the EShop README specification.

Which EShop requirements are suitable for use case testing?▼

Use case testing fits features with a clear user goal and multiple alternate flows, such as FR-08 checkout, FR-09 discount codes, FR-01 registration, FR-02 login, FR-03 password reset, and FR-16 CSV import. The Skill suggests candidates and waits for your selection.

What is the difference between a main success scenario and an extension?▼

The main success scenario is the happy path where the user goal is achieved. Extensions are alternate or exception flows branching from numbered steps, such as invalid input or locked accounts, and each extension gets at least one test case.

Does this Skill execute the tests against the real system?▼

Yes, step 3 runs the test cases against the live EShop system, records actual results and status, and writes one bug report file per failure. If execution is skipped, test cases are marked Not Run and no bug reports are created.

What output files does the use case testing workflow produce?▼

It produces a Use Case document, a test design analysis, individual markdown test cases under Test case/, bug reports under Bug Report/ when failures occur, and a traceability matrix linking scenarios, requirements, test cases, and bugs.