Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Guides

Loading

Aporeon

Technical interview practice, from one developer to another.

Guides About Editorial standards Support Privacy Terms Refund policy

Drills

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.

Search

Track

Practice style

Level

More filters1

Topic

Technology

Tech stack

Skill area

20 results across 1 active filter

Page 1 of 1

Comparison questionMedium~7 min

Choose between mocks, stubs, fakes, and real dependencies

Compares test doubles by purpose and explains when a real dependency provides a more trustworthy test.

Comparison questionMedium~7 min

Choose Testcontainers, SQLite, or EF Core InMemory

Chooses database test infrastructure by the provider behavior a test must prove.

.NETASP.NET CoreC#EF CoreSQL+2

Architecture scenarioMedium~10 min

Choose test coverage from change risk

Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.

.NETASP.NET CoreC#xUnit

Comparison questionEasy~5 min

Choose the right test level for a change

Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.

Architecture scenarioHard~12 min

Design a performance and load-test strategy

Designs realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.

.NETASP.NET CoreC#

Architecture scenarioMedium~10 min

Design tests for safe parallel execution

Uses unique namespaces and correctly scoped fixtures so parallel tests improve speed without creating collisions.

.NETASP.NET CoreC#EF CoreSQL+2

Debugging scenarioMedium~10 min

Diagnose and fix a flaky test

Treats flakiness as an observable defect in timing, state, order, infrastructure, or product behavior.

Concept questionMedium~7 min

Integration-test ASP.NET Core with WebApplicationFactory

Uses the real ASP.NET Core pipeline while replacing only environment-specific boundaries deliberately.

.NETASP.NET CoreC#xUnit

Comparison questionHard~9 min

Isolate database integration tests

Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.

.NETASP.NET CoreC#EF CoreSQL+2

Architecture scenarioHard~12 min

Keep a growing test suite fast and trustworthy

Designs a reliable CI test system with fast feedback, deliberate test stages, bounded parallelism, visible flakiness, useful diagnostics, and clear ownership.

Concept questionMedium~7 min

Make time, randomness, and generated ids testable

Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.

Concept questionEasy~5 min

Structure xUnit tests and fixture lifetimes

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.

Concept questionMedium~7 min

Test API contracts and compatibility

Combines schema diffing, real provider tests, consumer expectations, generated clients, semantic scenarios, and rollout evidence to prevent accidental API breaks.

.NETASP.NET CoreC#xUnit

Concept questionMedium~7 min

Test async code, cancellation, and timeouts

Tests asynchronous completion, caller cancellation, owned timeouts, cleanup, and race-sensitive side effects deterministically with controlled dependencies and bounded diagnostics.

Architecture scenarioMedium~10 min

Test authorization and tenant isolation

Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.

.NETASP.NET CoreC#xUnit

Architecture scenarioMedium~10 min

Test background workers and message consumers

Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.

.NETC#SQL ServerxUnit

Concept questionMedium~7 min

Test behavior without freezing implementation

Distinguishes observable contracts from incidental calls while preserving important interaction assertions.

Architecture scenarioHard~12 min

Test database migrations and rolling compatibility

Verifies migration SQL, data preservation, production-provider behavior, mixed application versions, backfills, and expand-contract releases.

.NETC#EF CoreSQLSQL Server+1

Architecture scenarioHard~12 min

Test external dependency boundaries

Combines protocol stubs, contract checks, sandbox tests, and failure simulation without depending on live production services.

.NETASP.NET CoreC#xUnit

Concept questionEasy~5 min

What makes a unit test valuable?

Focuses unit tests on stable behavior, meaningful boundaries, deterministic outcomes, and useful failure messages.