skills.rest
DuyITLOR
DuyITLORCOMMUNITY
Explore all skills by this author →
GitHub

Use Case Testing

Generates use case specifications, test scenarios, test cases, and bug reports from functional requirements.

Updated Jun 8, 2026
Search Tags:#bug report#software testing#test design#test cases#black-box testing#scenario matrix#use case testing
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill use-case-testing-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Use Case Testing
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.agents/skills/Use%20Case%20Testing
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill use-case-testing-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing systematic black-box tests from functional specifications is time-consuming and error-prone. This Skill automates the Use Case Testing technique: it reads a system's requirements specification, builds a formal Use Case Specification (actors, preconditions, main/alternative/exception flows), derives a Scenario Matrix, generates one detailed test case file per scenario, executes the tests against the running application, and produces structured bug reports for any failures. ## Core Features & Use Cases - Use Case Specification Generation: Builds complete use cases with Main Flow (S1, S2...), Alternative Flows (AF1...), and Exception Flows (EF1...) strictly grounded in the requirements document, with explicit branch points. - Scenario Matrix & Test Case Files: Derives every path through the use case as a scenario (e.g., FR10-UCT-01) and creates one Markdown test case file per scenario with preconditions, test data, steps, expected/actual results, and status. - Test Execution & Bug Reporting: Runs the test cases against the live application, updates Actual results and Status (Passed/Failed/Blocked), and writes standardized bug reports with optional screenshot evidence for failed cases. - Use Case: Given the EShop order state machine requirement (FR-10), the Skill produces UC-FR10 with 8 scenarios covering the happy path, user/admin cancellations, and invalid transitions, then generates 8 test case files and a bug report when it finds that a canceled order can be moved to delivered. ## Quick Start Ask the assistant to apply Use Case Testing to a specific functional requirement (e.g., "Run Use Case Testing for FR-10 order status management") and it will produce the test design, test cases, execution results, and bug reports.

Frequently Asked Questions about Use Case Testing

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

FAQPage Schema
How do I create test cases using the Use Case Testing technique?▼

Use Case Testing builds a use case specification with a Main Flow, Alternative Flows, and Exception Flows from the requirements, then derives one test scenario per path through those flows. Each scenario becomes a detailed test case with preconditions, test data, steps, and expected results.

What is the difference between main flow, alternative flow, and exception flow in use case testing?▼

The Main Flow is the successful happy path from start to finish. Alternative Flows are valid branches that still succeed differently, while Exception Flows are error or violation paths that end in failure or blocked actions. Each flow must state its branch point from the Main Flow.

When is Use Case Testing not applicable to a feature?▼

Use Case Testing does not fit features that are too simple, such as single-step operations with no alternative or exception flows. In that case the Skill reports that the technique cannot be applied and explains why instead of forcing a design.

How are test scenarios derived from a use case specification?▼

Each scenario is one path through the use case: the full Main Flow, the Main Flow up to a branch point plus an Alternative Flow, or a path into an Exception Flow. Scenarios are listed in a Scenario Matrix with ID, path, and expected result, and each maps to exactly one test case file.

What happens when a test case fails during execution?▼

The test case file is updated with the actual results and a Failed status, and a separate bug report file is created describing the defect, reproduction steps, expected versus actual results, and optional screenshot evidence stored in an images folder.

Related Skills

Explore More Software Engineering Skills→
Avila-TekAvila-Tek

functional-spec-generator

Convert design documents into a 9-section Functional Spec in Spanish Markdown.

Official
Advanced
reddya3reddya3

qa-test-executor

Execute manual QA test cases and capture pass/fail evidence.

Community
Advanced
CENKSSSCENKSSS

test-design-techniques

Generate test cases using Boundary Value Analysis, Equivalence Partitioning, Decision Tables, and Pairwise Testing.

Community
Advanced
AZANIRAZANIR
2

qa-manual-test-designer

Design manual test cases and exploratory testing charters using specification-based techniques.

Community
Intermediate