Skip to content

v0.12.0 — Test a stub without leaving the dashboard

Choose a tag to compare

View all tags
@omercelikdev omercelikdev released this 27 Jul 10:58
v0.12.0
4defed2

The stub editor gains a built-in request runner (#203) — try a stub the moment you write it, no curl or Postman needed.

Stub test runner

  • A Test button on HTTP and GraphQL stubs opens a request dialog: method, URL and Send on top; Params / Headers / Body tabs below
  • Pre-filled from the stub's matchers — equalTo headers and query params, the first equalTo/equalToJson body pattern, and an automatic Content-Type: application/json when the body is JSON; unsaved editor changes count
  • A real request: it runs the full serving pipeline — environment {{key}}s resolve server-side, scenarios advance, and the call lands in the request journal like any traffic; {{key}}s also preview inline before sending
  • Response view in the journal's visual language: status chip, duration, size, headers, pretty-printed body — plus Copy body, Copy as curl, and a body Beautify
  • Connection failures and timeouts surface inline; closing and reopening re-seeds from the stub's current configuration
  • gRPC/WebSocket stubs hide the button (a plain HTTP probe can't exercise them); all six dashboard locales translated

Validation: verified in-browser against a live host — matched 200 with server-resolved environment values, unmatched 404, network-error banner, reopen-reset, and both test calls visible in the journal. tsc/lint/build clean; no engine or server change, differential suite green.

Docs: dashboard guide updated.

🤖 Generated with Claude Code

Assets 2
Loading