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.
59 results across 1 active filter
Page 2 of 3
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.
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.
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.
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.
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.
Tests user-observable urgent, pending, success, failure, interruption, and out-of-order behavior without scheduler coupling.
Uses profiler evidence to isolate expensive derived data and row rendering, then applies memoization without hiding correctness bugs.
Diagnoses incompatible cached HTML and immutable assets across CDN, browser, service-worker, and rollout boundaries.
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.
Diagnoses aliasing and shallow-copy mistakes, then restores explicit state ownership and immutable update boundaries.
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.
Handles expected failures at their callsite and reserves ErrorHandler for reporting unexpected framework or global failures with useful context.
Handles eager subscription, initial values, injection context, errors, cleanup, and repeated conversions.