experience-scenario

Designs black-box test cases from use case flows, realistic scenarios, and grammar mutations.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill experience-scenario-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experience-scenario
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/experience-scenario
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill experience-scenario-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It helps testers catch defects that specification-structure-based techniques miss by deriving test cases from business flows, realistic usage stories, and input grammar violations rather than from the spec's mechanical structure. ## Core Features & Use Cases - Use Case Testing: Maps each main success flow, alternative flow, and exception flow of a use case into one test case each, with emphasis on exception coverage. - Scenario Testing: Builds end-to-end tests from realistic multi-use-case paths (e.g., subscribe, cancel, re-register) grounded in real logs or usage data, with intermediate assertions for fault isolation. - Syntax Testing: Generates valid inputs plus single-mutation invalid inputs (omission, extra, reordering, type violation) from a BNF or regex grammar to validate parsers and validators. - Use Case: When testing a date parser accepting YYYY-MM-DD, enumerate the grammar productions, write acceptance cases for valid dates, and one rejection case per single-production mutation such as a missing digit or extra separator. ## Quick Start Ask the AI to apply use case, scenario, and syntax testing techniques from this catalog to design test cases for your feature's flows and input formats.

Frequently Asked Questions about experience-scenario

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

FAQPage Schema
How do I design test cases from use case flows?

Enumerate the basic flow, alternative flows, and exception flows from the use case description, then map each flow to exactly one test case. Concretize preconditions like actor, stock, and permissions per branch, and prioritize exception flows since they carry the most defect-finding value.

What is scenario testing and when should I use it?

Scenario testing verifies realistic operation sequences spanning multiple use cases, such as subscribe, cancel, then re-register. Use it when individual features pass but combined real-world usage might break; base scenarios on actual logs or usage data rather than imagined paths.

How does syntax testing generate invalid inputs?

Syntax testing writes the input format as BNF or a regular expression, then creates one invalid input per production by applying a single mutation: omission, extra element, reordering, or type violation. Keeping one mutation per case ensures you know which grammar rule rejected the input.

Can scenario-based techniques replace systematic test design?

No, these techniques do not claim standalone coverage and act as a finishing layer on top of systematic methods like equivalence partitioning and state transition testing. Defects found should be written back into systematic techniques as regression tests.

Why should syntax tests avoid breaking multiple grammar rules at once?

Breaking multiple rules in one input makes it impossible to tell which rule caused the rejection, defeating fault isolation. Keep one mutation per test case, and also include valid-input acceptance cases so a parser that always returns false is still caught.