Loading
Pick a focused question that fits your time, stack, and interview goal.
15 results across 1 active filter
Page 1 of 1
Turns a production-only role and payload failure into the smallest durable API regression test.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Pairs a bounded isolated reproduction with telemetry and a disposal fix for leaked database connections.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
Builds a bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
Uses WebApplicationFactory with test-only authentication and isolated dependencies to exercise the real ASP.NET Core pipeline.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Expresses allowed and denied capability combinations as one parameterized API integration test.
Proves repeated requests with one idempotency key create one resource and return a consistent result.
Proves that one authenticated user cannot read or modify another user's private resource.
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.
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.