Skip to content

v0.6.0 — Schema-driven negative testing

Choose a tag to compare

View all tags
@YuCPbit YuCPbit released this 20 Aug 22:39
· 9 commits to main since this release
v0.6.0
732191b

The audit learns to ask the question schemas only imply: does the server enforce what it declares?

  • Two-phase argument synthesis: local $ref resolution, allOf merging, const, deterministic pattern candidates, format seeds, exclusive bounds, multipleOf snapping, minItems/maxItems — same schema, same args, every run.
  • Verified negative variants: the valid baseline with exactly one field pushed past a declared constraint. Every candidate is checked with jsonschema before use — a finding can never be a generation artifact. (Boolean type-flips use an int: lax validators coerce "yes"-style strings.)
  • TOOL-07 (SHOULD, both eras): up to two verified-invalid inputs against up to three side-effect-safe tools; a normal answer earns a WARN quoting the minimal reproducer:
TOOL-07  WARN  declared constraints not enforced — echo: minimal invalid input (text=oversized) was answered normally

77 tests · CHANGELOG

Assets 2
Loading