Run any Skill in Manus with one click

boundary-value-analysis

Stars0

Forks0

UpdatedMay 13, 2026 at 06:22

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jovd83

jovd83/test-design-orchestrator

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	boundary-value-analysis
description	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.
metadata	{"author":"jovd83","version":"v2.0.0","dispatcher-output-artifacts":"boundary_partitions, test_cases, coverage_summary","dispatcher-risk":"low","dispatcher-writes-files":true,"dispatcher-input-artifacts":"requirements, value_ranges, constraints, traceability_context","dispatcher-capabilities":"test-design, boundary-value-analysis, partition-design","dispatcher-stack-tags":"testing, design, boundary-analysis","dispatcher-accepted-intents":"design_boundary_value_tests, identify_boundary_conditions","dispatcher-category":"testing"}

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.

More from this repository

same repository

test-design-orchestrator

jovd83/test-design-orchestrator

Turn requirements, user stories, acceptance criteria, business rules, use cases, or state models into structured test artifacts. Selects the best black-box test design technique and routes work to the matching subskill. For format-only work, prefer test-artifact-export-skill.

2026-05-130

acceptance-criteria-to-test-cases

jovd83/test-design-orchestrator

Use this skill when Codex needs to convert user stories or acceptance criteria into traceable behavior-focused scenarios or structured test cases.

2026-05-130

classification-tree-nwise

jovd83/test-design-orchestrator

Use this skill when Codex needs to model interacting parameters and generate reduced pairwise or n-wise combinations instead of an impractical full Cartesian set.

2026-05-130

decision-table

jovd83/test-design-orchestrator

Use this skill when requirements describe discrete business rules, multiple conditions, or outcome logic that should be modeled as a rule table.

2026-05-130

equivalence-partitioning

jovd83/test-design-orchestrator

Use this skill when Codex needs to derive representative tests from input classes that should behave the same within each valid or invalid partition.

2026-05-130

state-transition

jovd83/test-design-orchestrator

Use this skill when a system has discrete states, events, guards, or lifecycle phases and Codex needs transition-focused test design.

2026-05-130

name	boundary-value-analysis
description	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.
metadata	{"author":"jovd83","version":"v2.0.0","dispatcher-output-artifacts":"boundary_partitions, test_cases, coverage_summary","dispatcher-risk":"low","dispatcher-writes-files":true,"dispatcher-input-artifacts":"requirements, value_ranges, constraints, traceability_context","dispatcher-capabilities":"test-design, boundary-value-analysis, partition-design","dispatcher-stack-tags":"testing, design, boundary-analysis","dispatcher-accepted-intents":"design_boundary_value_tests, identify_boundary_conditions","dispatcher-category":"testing"}

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.