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.
176 results across 1 active filter
Page 4 of 8
Uses HttpTestingController to verify request semantics and return controlled responses without calling a real server.
Uses a real route configuration and RouterTestingHarness to verify URLs, rendered components, redirects, guards, and failures.
Controls virtual time and completion order to prove debounce, switching, retries, and teardown without sleeping in tests.
Exercises signal-based component contracts through Angular bindings and waits for scheduled rendering before asserting.
Separates interruptible background rendering from time-based event or request suppression.
Combines a canonical detail page with an intercepted modal, Parallel Route slot, browser history, and accessible dismissal.
Chooses browser storage by server transport, lifetime, capacity, query needs, sensitivity, synchronization, and offline behavior.
Places validation at the right form level and manages asynchronous checks without races or noisy requests.
Balances route ownership, initial bundle cost, likely navigation, authorization, and measurable user experience.
Repairs unstable Hook order caused by branches, early returns, callbacks, loops, or exception paths.
Uses repeatable navigation, heap evidence, retained-object paths, and ownership checks to find subscriptions, listeners, and DOM retained past teardown.
Moves from a reproducible user interaction to render evidence, root cause, proportional repair, and field validation.
Places each risk at the cheapest reliable test boundary and keeps a small set of browser journeys for integration confidence.
Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.
Combines safe bindings, AOT, dependency discipline, CSP, Trusted Types, and reporting without treating one control as a complete defense.
Combines server and client instrumentation, OpenTelemetry, post-response work, correlation, and privacy-aware signals.
Owns a third-party widget through a DOM ref, effect lifecycle, minimal updates, and complete teardown.
Models pending, validation, success, retry, and authoritative server outcomes around a React 19 form Action.
Uses semantic forms, action state, pending feedback, server validation, focus behavior, and progressive enhancement.
Splits meaningful code, keeps stable UI visible, preloads likely paths, and pairs loading with error recovery.
Uses supported version steps, ng update migrations, dependency compatibility, targeted cleanup, and staged production evidence.
Treats actions as public mutation endpoints with server validation, fresh authorization, idempotency, transactions, and safe errors.
Designs explicit ESM boundaries with focused exports, controlled side effects, and dependency direction that supports safe bundling.
Combines semantic queries, keyboard interaction, focus assertions, and automated checks while retaining manual assistive-technology review.