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.
106 results across 1 active filter
Page 3 of 5
Applies an immediate reversible mutation, blocks overlapping writes, and restores the previous state on failure.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
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.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
Guards a mutation immediately, exposes pending state, and restores the command after failure.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Builds a typed functional canDeactivate guard and editor contract that protects dirty work until a save has actually succeeded.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Uses fake time and HttpTestingController to complete requests out of order and prove latest-query state, recovery, and teardown.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Uses server-resolved capabilities for presentation while keeping the mutation endpoint authoritative.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Persists a job and outbox command before returning a status URL for long-running work.
Produces field-keyed validation errors through one reusable endpoint boundary.
Keeps data and secrets on the server while sending a small serializable model to an interactive client component.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
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.
Makes list filters shareable and back-button friendly while resetting pagination deliberately.