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.
34 results across 1 active filter
Page 1 of 2
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.
Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.
Treats flakiness as an observable defect in timing, state, order, infrastructure, or product behavior.
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 the real ASP.NET Core pipeline while replacing only environment-specific boundaries deliberately.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Designs a reliable CI test system with fast feedback, deliberate test stages, bounded parallelism, visible flakiness, useful diagnostics, and clear ownership.
Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Structures xUnit tests around per-test instances and shares only expensive infrastructure through deliberate class, collection, or assembly fixture lifetimes while preserving isolation and parallel safety.
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.
Combines schema diffing, real provider tests, consumer expectations, generated clients, semantic scenarios, and rollout evidence to prevent accidental API breaks.
Proves that one authenticated user cannot read or modify another user's private resource.
Tests asynchronous completion, caller cancellation, owned timeouts, cleanup, and race-sensitive side effects deterministically with controlled dependencies and bounded diagnostics.
Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.