Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
8 results across 1 active filter
Page 1 of 1
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Builds a bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Proves repeated requests with one idempotency key create one resource and return a consistent result.
Combines schema diffing, real provider tests, consumer expectations, generated clients, semantic scenarios, and rollout evidence to prevent accidental API breaks.
Uses a controllable fake HTTP handler to prove request cancellation reaches a downstream dependency.
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.