Loading
Pick a focused question that fits your time, stack, and interview goal.
20 results across 1 active filter
Page 1 of 1
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 realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.
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.
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.
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.
Combines schema diffing, real provider tests, consumer expectations, generated clients, semantic scenarios, and rollout evidence to prevent accidental API breaks.
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.
Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.
Distinguishes observable contracts from incidental calls while preserving important interaction assertions.
Verifies migration SQL, data preservation, production-provider behavior, mixed application versions, backfills, and expand-contract releases.
Combines protocol stubs, contract checks, sandbox tests, and failure simulation without depending on live production services.
Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.