Releases: nchaugen/tabletest-claude-plugin
Releases · nchaugen/tabletest-claude-plugin
v1.3.0
Changes
Changed
- tabletest: Simplified pre-check — dependency and shape checks rewritten as readable prose rather than a prescriptive checklist
- tabletest: Improved skill trigger description so the skill activates on value-set, type-converter, and column-design questions even when the user doesn't say "TableTest" explicitly
- tabletest: Pair programming guidance extracted to
references/pair-programming.md; SKILL.md retains the key habit (show a mockup first) with a pointer to the full cadence - spec-by-example: Improved skill trigger description — now activates on vague requirements and mid-implementation edge cases, not just upfront spec work
- spec-by-example: Expanded value-set guidance with a dedicated state/status example (
{PENDING, CONFIRMED}) and an explicit callout that blank and value-set mean different things and must not be conflated - spec-by-example: Clearer handoff section linking to
/tabletestwith column-translation notes
Added
- tabletest: Date format limitation warning — built-in
LocalDate/LocalDateTimeconversion handles ISO 8601 only; non-standard formats require a@TypeConverter - Plugin: Updated description to cover both skills; keywords updated (
spec-by-example,example mappingadded;fit,acceptance testingremoved)
Full changelog: https://github.com/nchaugen/tabletest-claude-plugin/blob/main/CHANGELOG.md
v1.2.0
Added
- Spec-by-example skill (
/spec-by-example) for clarifying behaviour with multiple cases or rules through concrete example tables- Elicitation workflow: naming the concern, finding the first example, identifying columns, probing for edge cases and irrelevant inputs
- Example table design principles: one concern per table, business language throughout, concrete domain values, traceable outputs, thresholds visible as columns, conditions as scenario names
- Multiple-table guidance: when to split, how to let additional tables emerge naturally
- Bridge from example table to
@TableTest: direct column mapping, value set carry-over, handoff to/tabletestskill - Quality checklist for example tables
v1.1.0
Added
- Non-obvious built-in type conversions reference table (enums, hex/octal integers,
Class<?>variants,Duration,Period,Currency,Locale) - Minimal quoting strategy: start without quotes, add only where needed
- Guidance on quoting inside collection elements rather than wrapping the whole collection
- Newline handling in table values (
\\n+ manual replace in test method) - Set
{}vs List[]common mistake callout - Single-scenario
@TableTestexception in pre-check - Guidance on when NOT to use TableTest (trivial implementations, complex setup, already covered by integration tests)
- New advanced design pattern: separate tables when column sets diverge
- New common pattern: static constants for readable expected values (e.g. ANSI codes)
v1.0.0
Added
- TableTest skill for writing and converting JUnit tests to TableTest format
- Reference guides: dependency setup, value sets, type converters, column design, common patterns, large tables, example patterns, async and performance, provided parameters, advanced table design, incremental development, consolidating tests, testing reveals bugs