Loading
Pick a focused question that fits your time, stack, and interview goal.
73 results across 1 active filter
Page 2 of 4
Moves non-deterministic browser-only rendering behind a stable server snapshot and post-hydration update.
Uses a test-only DbCommandInterceptor to fail a regression when database command count grows with page size.
Separates caller cancellation from a dependency timeout and maps expected downstream outcomes safely.
Validates size and signature, writes under a generated storage key, and keeps untrusted files outside the public web root.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Builds a bounded readiness check for one required dependency while keeping liveness independent and responses non-sensitive.
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.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
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.