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.
24 results across 1 active filter
Page 1 of 1
Finds failures hidden by test-owned transactions, automatic rollback, open persistence contexts, missing flushes, and separate server threads.
Separates authentication orchestration, mechanism-specific verification, and username-based user lookup.
Traces a Servlet request through the security proxy, selected filter chain, authentication, context, authorization, and exception handling.
Improves suite speed by reusing stable application contexts and avoiding configuration variation, unnecessary dirtiness, and process forks.
Explains first-match chain selection, rule matching inside a chain, ordering, fallback coverage, and accidental unprotected paths.
Treats GrantedAuthority as the common representation while explaining role prefixes, scope mapping, and domain permission design.
Selects the smallest Spring test scope that can prove the risky boundary without mocking away framework or infrastructure behavior.
Separates authentication challenge from denied authorization and traces the selected entry point, denied handler, and matched rule.
Tests serialization, headers, status mapping, timeouts, and retries against a controllable HTTP boundary instead of mocking fluent internals.
Tests anonymous, authenticated, forbidden, CSRF, JWT, method, ownership, and full credential flows without confusing mocked identity with authentication.
Constructs a service directly with explicit collaborators and verifies behavior without Spring startup or framework-owned concerns.
Runs stable shared production-like dependencies with Spring service connections, real migrations, deterministic data, and bounded startup cost.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Stores salted adaptive password hashes, supports algorithm migration, and separates password verification from encryption.
Explains the request identity model, principal and authorities, default thread-local storage, cleanup, and asynchronous boundaries.
Uses the JPA slice for mappings and repositories while recognizing embedded-database substitutions and transaction-owned blind spots.
Separates proving an identity from deciding whether that identity may perform a specific action on a resource.
Separates full Spring MVC dispatch over mock Servlet objects from tests that cross an actual network and container boundary.
Separates logging a user into an application, obtaining tokens for outbound calls, and validating access tokens on an API.
Uses HTTP rules for route-level policy and method security for reusable service operations without creating contradictory enforcement.
Chooses credential transport and server state from client shape, revocation, browser threats, scaling, and operational requirements.
Chooses a focused MVC slice or full application context based on whether the risk is the web contract or complete wiring.
Bases CSRF policy on whether browsers automatically attach credentials and keeps unsafe requests protected without disabling security globally.
Overrides unstable external boundaries intentionally while keeping the framework behavior and real collaborators the test claims to prove.