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.
52 results across 1 active filter
Page 2 of 3
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.
Uses repeatable navigation, heap evidence, retained-object paths, and ownership checks to find subscriptions, listeners, and DOM retained past teardown.
Places each risk at the cheapest reliable test boundary and keeps a small set of browser journeys for integration confidence.
Combines safe bindings, AOT, dependency discipline, CSP, Trusted Types, and reporting without treating one control as a complete defense.
Uses supported version steps, ng update migrations, dependency compatibility, targeted cleanup, and staged production evidence.
Combines semantic queries, keyboard interaction, focus assertions, and automated checks while retaining manual assistive-technology review.
Builds a typed functional canDeactivate guard and editor contract that protects dirty work until a save has actually succeeded.
Uses fake time and HttpTestingController to complete requests out of order and prove latest-query state, recovery, and teardown.
Wraps widget creation, listeners, observers, timers, and destruction in one lifecycle boundary and verifies repeated navigation does not accumulate resources.
Tests input replacement, DOM events, computed rendering, and stable identity without forcing change detection around missing notifications.
Handles expected failures at their callsite and reserves ErrorHandler for reporting unexpected framework or global failures with useful context.
Uses functional interceptors for cross-cutting transport concerns without hiding domain behavior or unsafe retries.
Handles eager subscription, initial values, injection context, errors, cleanup, and repeated conversions.
Tests rendered behavior, user interaction, outputs, and visible failure states without coupling to private implementation details.
Uses harnesses for reusable or complex widgets where a stable user-oriented test API is more valuable than direct DOM coupling.
Uses runtime tokens for configuration and abstractions while distinguishing provider recipes and instance identity.
Separates source state, derived state, and synchronization with external systems to prevent reactive loops.
Defers non-critical UI with deliberate triggers, placeholders, prefetching, and hydration behavior while protecting core interactions.
Chooses between blocking navigation for essential data and rendering a page-owned loading state.
Chooses between synchronous UI state and asynchronous event streams without treating either model as a replacement for the other.
Distinguishes one-way data, events, and deliberate two-way component contracts without hiding ownership.
Finds missing render notifications that forced test change detection can hide and uses production-like stability checks.
Diagnoses server fallback rules, deployment base paths, asset URLs, and cache behavior rather than changing Angular routes blindly.