agentsclimarketplace
Sign in

Use case testing

Skill jovd83/test-design-orchestrator/use-case-testing

Use this skill when requirements are expressed as actor-system interactions with preconditions, main flows, alternate flows, and postconditions.From its SKILL.md

Install
npx -y skills add jovd83/test-design-orchestrator --skill use-case-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 186 tokens by cl100k_base, as published. Nobody here has run it

Use Case Testing

Read First

  • ./references/use-case-testing.md
  • ./references/test-design-shared-conventions.md
  • ./assets/templates/test-case-table.j2
  • ./assets/templates/test-case.j2

Workflow

  1. Extract actor, trigger, preconditions, main success scenario, alternate flows, exceptions, and postconditions.
  2. Generate at least one scenario for the main flow.
  3. Generate separate scenarios for each alternate or exception path that changes system behavior or outcome.
  4. Keep the path reference visible in every generated scenario.

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.