Testing Async and SSE Flows as a Scenario
Long-running and streaming work still needs ordered, connected verification.
Read articleThe Powerduck Blog
API engineering, from the spec out
Product updates, engineering notes, and guides for designing, debugging, testing, mocking, and serving MCP tools from one OpenAPI spec.
Browse the guidesTesting an A2A JSON-RPC Error Inside a 200
The HTTP layer and the JSON-RPC layer can disagree.
Read articleTesting a Checkout Flow End to End
A checkout flow is a classic multi-step scenario with real dependencies.
Read articleTable Status: Missing, Drift, Matched, Extra
The status makes the table-level comparison explicit.
Read articleStreaming A2A Task Status over SSE
SSE keeps long-running task progress visible as it happens.
Read articleStatic vs Dynamic Evidence in Code Review
Static and dynamic evidence answer different questions; use both and know the gap.
Read articleStatic Scanning Without a Model Key
The deterministic scan works offline with no model or provider key.
Read articleScenario Testing vs Single Endpoint Testing
Both have a place; the difference is the unit they verify.
Read articleReviewing Detected Routes Before Adopting a Spec
Treat the scanned document as a draft to verify before you adopt it.
Read articleReviewing a PR with Git Diff and Context
A diff is only the start; the surrounding context is what makes a review reliable.
Read articleRescanning Incrementally Without Losing Edits
The sidecar keeps rescans fast and your manual edits intact.
Read articleReading an HTML Scenario Test Report
The report is a shareable record of exactly what each step did.
Read article