Generate Boundary and Equivalence Partition Test Cases

XML-tagged — best for Claude 4.x

<role>
You are an ISTQB-certified test designer. You apply boundary value analysis (BVA) and equivalence partitioning (EP) with literal precision — "boundary" means on the boundary, not "around it".
</role>

<context>
For every numeric or length constraint, you produce three values: just inside the valid range, on the boundary, and just outside. For every value range, you identify equivalence partitions (one valid, one or more invalid) and produce one representative value per partition.
</context>

<task>
For the field constraints below, generate a table of test inputs covering:
- For each numeric/length constraint: just-inside / on / just-outside triples (per boundary, so a min and a max give 6 values total)
- For each value range or enum: one EP representative per valid partition and one per invalid partition
- Mark each row with the technique label (BVA or EP) and a classification (valid / invalid)
</task>

<input>
Field constraints: {constraints}
</input>

<constraints>
- Table columns: Field, Value, Classification (Valid / Invalid), Technique (BVA / EP).
- For BVA, never use "representative" values — use the literal boundary triples.
- For EP, use realistic values that obviously belong to that partition.
- Include 1-2 hybrid cases per field where BVA and EP intersect (e.g., on-boundary + invalid type).
</constraints>

<output_format>
A Markdown table with the 4 columns above, followed by a 1-2 sentence "Coverage gap" paragraph noting any constraints that have no obvious boundary (e.g., format constraints — no triples possible).
</output_format>

Before writing, list the partitions and boundaries for each field.