Loading
Pick a focused question that fits your time, stack, and interview goal.
34 results across 1 active filter
Page 2 of 2
Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.
Distinguishes observable contracts from incidental calls while preserving important interaction assertions.
Uses a controllable fake HTTP handler to prove request cancellation reaches a downstream dependency.
Verifies migration SQL, data preservation, production-provider behavior, mixed application versions, backfills, and expand-contract releases.
Combines protocol stubs, contract checks, sandbox tests, and failure simulation without depending on live production services.
Walks API pages through equal sort values and verifies no duplicate or missing resource ids.
Verifies status, content type, stable error extensions, and field errors for an invalid API request.
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.