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.
73 results across 1 active filter
Page 1 of 4
Explains labels, keyboard behavior, focus, semantic HTML, errors, color contrast, and accessible custom controls.
Turns a production-only role and payload failure into the smallest durable API regression test.
Partitions limits by authenticated user or trusted client address and returns useful 429 retry metadata.
Loads a resource once, evaluates owner-or-capability authorization, and avoids trusting route ownership claims.
Implements labeled fields, client validation, error summaries, focus recovery, and pending submission state.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Builds a route-level Next.js failure UI with safe reporting, retry, and an escape route while keeping expected errors out of the boundary.
Implements bounded filtering and deterministic keyset pagination without accepting arbitrary query expressions.
Creates a resource through an explicit request DTO and returns typed 201, 409, and validation outcomes.
Models file validation, progress, cancellation, failure, and retry without losing the selected file.
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.
Designs useful local database and cache resources without confusing container lifetime, durable data, bind mounts, parameters, and production secrets.
Combines debounce cleanup, AbortController, and request identity to prevent stale search results.
Explains a practical debugging path across browser, Next.js layer, API, logs, database, and deployment changes.
Designs realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.
Builds a risk-based frontend test strategy across unit, component, integration, contract, and end-to-end 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.
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Treats JSON serialization settings and DTO shape as a public contract, including naming, enums, nulls, converters, compatibility, and tests.