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.
65 results across 1 active filter
Page 3 of 3
Makes list filters shareable and back-button friendly while resetting pagination deliberately.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Tests one browser-to-database practice workflow with isolated fixtures, resilient locators, durable assertions, and reliable cleanup.
Explains component tests that assert user-visible behavior instead of implementation details.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Balances strict script policy with per-request nonces, dynamic rendering, third-party scripts, caching, and operational rollout.
Keeps Next.js 16 Proxy focused on request routing and optimistic checks rather than data access or final authorization.
Defines the serializable prop boundary, component composition pattern, and protections against leaking server-only data.
Covers Promise-based params and search parameters, async request APIs, generated route types, and runtime validation.
Explains Next.js 16 explicit caching, static shells, dynamic islands, cache keys, and adoption boundaries.
Separates missing resources, canonical navigation, authorization outcomes, expected failures, and unexpected exceptions.
Connects layouts and templates to navigation, state lifetime, Effects, and deliberate remounting in the App Router.
Chooses between UI-coupled mutations and explicit HTTP contracts without treating either as a hidden trust boundary.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.