Integration test suite — generated per endpoint, and crucially including
the tests people skip because they're tedious, which are the ones that
catch real bugs.

STRUCTURE — per endpoint, not per "feature"
  POST /users
    ✓ 201 + body matches schema on valid input      (happy path)
    ✓ 400 on missing required field                  (validation)
    ✓ 400 on wrong type (string where int expected)
    ✓ 401 without auth token                         (auth)
    ✓ 403 with valid token, wrong permissions        ← usually skipped
    ✓ 409 on duplicate email                         (conflict)
    ✓ 422 on malformed but well-typed input
  GET /users?page=2
    ✓ pagination returns correct slice + total count
    ✓ empty result set returns [] not null           ← the null bug
    ✓ out-of-range page returns empty, not error

THE TESTS THAT ACTUALLY FIND BUGS
Happy-path tests pass on day one and rarely fail again. The value is in:
  • the 403 case (valid token, wrong role) — the most common real auth
    hole, and the most commonly untested
  • empty-result shape ("[]" vs "null") — breaks clients silently
  • the boundary between 400 and 422 — malformed vs. invalid
These are what I generate by default, because a suite that only tests
happy paths gives false confidence.

CONTRACT TESTS
If you have an OpenAPI spec, I generate tests that assert every response
matches the declared schema — so a backend change that drifts from the
contract fails CI instead of breaking a client in prod.

WHAT I NEED
The endpoints or an OpenAPI spec. With a spec I can generate the full
suite including contract tests; without one I generate from the endpoint
list and you fill in the auth model. Which do you have?