boundary-value-analysis

Generates boundary value analysis test cases for ordered input variables from feature specifications.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill boundary-value-analysis-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: boundary-value-analysis
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/HW/week03/NhutDuy/submission/agent-skills/boundary-value-analysis
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill boundary-value-analysis-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing test cases at the edges of input ranges is where defects cluster, yet testers often miss boundaries, confuse inclusive and exclusive limits, or stop at the lower bound. This Skill walks you through Boundary Value Analysis (BVA) step by step so every ordered variable gets systematic edge coverage. ## Core Features & Use Cases - Variable Selection & Boundary Identification: Filters variables with ordered, bounded domains (numbers, dates, string lengths, quantities) and documents each lower/upper bound with inclusive/exclusive semantics and units. - 3-Point Boundary Generation: Produces B-1, B, B+1 values around each valid min/max, adapting step size to the data type (1 for integers, smallest unit for decimals, 1 day for dates, 1 char for lengths). - Structured Test-Case Tables: Outputs a boundary table plus a BVA test-case table with IDs like BVA-<FR>-001, expected results, and pass/reject verdicts, written to test-cases/feature-<X>/boundary-value-analysis.md. - Use Case: Given a spec requiring passwords of 8-32 characters, generate test cases for lengths 7, 8, 9, 31, 32, and 33, marking which should pass and which should be rejected. ## Quick Start Apply boundary value analysis to the password length requirement in FR-01 and produce the boundary table and BVA test-case table.

Frequently Asked Questions about boundary-value-analysis

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

FAQPage Schema
How do I apply boundary value analysis to a feature specification?▼

Boundary value analysis selects variables with ordered, bounded domains, identifies each valid min and max, then generates B-1, B, and B+1 values per boundary. Each boundary value becomes one test case while other variables stay at valid values.

What is the difference between 2-point and 3-point boundary value analysis?▼

3-point BVA tests B-1, B, and B+1 around each boundary, giving six points across two bounds. 2-point BVA tests only the boundary B and the invalid B±1, and is used only when explicitly required.

Which input variables are eligible for boundary value analysis?▼

Only variables with ordered, bounded domains qualify: numeric ranges, string lengths, counts, dates, and money amounts. Unordered or enumerated variables are excluded and remain covered by domain or equivalence partitioning testing.

Why does inclusive versus exclusive boundary matter in BVA?▼

Inclusive versus exclusive bounds change the on/off points of a range, so a wrong assumption produces incorrect test values. Stating inclusivity explicitly is the most common BVA mistake and must be recorded for every variable.

When should I use boundary value analysis instead of equivalence partitioning?▼

Use BVA after or alongside equivalence partitioning when variables have ordered ranges, since defects cluster at partition edges. Equivalence partitioning alone covers representative values but does not systematically target boundary behavior.