Boundary value analysis

Skill jovd83/test-design-orchestrator/boundary-value-analysis

Use this skill when a requirement contains ordered values such as ranges, lengths, dates, counts, or sequence limits and Codex needs boundary-focused test scenarios.From its SKILL.md

Install

npx -y skills add jovd83/test-design-orchestrator --skill boundary-value-analysis

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.9 KB, 253 tokens by cl100k_base, as published. Nobody here has run it

Boundary Value Analysis

Read First

./references/boundary-value-analysis.md
./references/test-design-shared-conventions.md
./assets/templates/partition-table.j2
./assets/templates/test-case-table.j2
./assets/templates/test-case.j2

Workflow

Confirm the requirement has a true ordered boundary.
Extract each condition with its inclusive or exclusive limits.
If inclusivity, units, or the meaning of zero are unclear, ask before proceeding.
Use 3-value BVA by default: just below, on, and just above each boundary.
Use 2-value BVA only when the user explicitly asks for it.
Generate tests that keep the cause of failure obvious. Avoid combining multiple invalid boundaries in one test unless the user asks for stress coverage.

Required Output

boundary inventory
boundary-to-test mapping
detailed or summarized test cases, depending on the user's requested level of detail
coverage note describing which boundaries were exercised

Guardrails

Do not treat unordered categories as BVA candidates.
Do not invent boundaries that are not implied by the requirement.
Separate inferred boundaries from stated ones.

What ships with it

Read from the repository

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