Use Case Testing

Required Output

• use-case summary
• path inventory
• scenario list or detailed test cases
• coverage note showing which flows are covered

Guardrails

• Do not rewrite the use case into lower-level rule tables unless the user asks for a secondary pass.
• Do not skip postcondition checks on alternate paths.37:["$","$L3e",null,{"content":"$3f","frontMatter":{"name":"use-case-testing","description":"Use this skill when requirements are expressed as actor-system interactions with preconditions, main flows, alternate flows, and postconditions.","metadata":{"author":"jovd83","version":"v2.0.0","dispatcher-output-artifacts":"use_case_tests, flow_map, coverage_summary","dispatcher-risk":"low","dispatcher-writes-files":true,"dispatcher-input-artifacts":"use_case, actor_flows, preconditions, postconditions","dispatcher-capabilities":"test-design, use-case-analysis, flow-based-scenario-generation","dispatcher-stack-tags":"testing, design, use-case","dispatcher-accepted-intents":"design_use_case_tests, model_actor_system_flows","dispatcher-category":"testing"}}}]