Route based on what the user is testing. If no specific slice annotation is visible and the domain is unclear, default to spring-testing-fundamentals.
Routing Table
| The user is testing... | Load this skill |
|---|---|
| JPA repositories, Spring Data queries, database persistence | spring-jpa-testing |
| REST controllers, HTTP endpoints, MockMvc | spring-mvc-testing |
| Authentication, authorization, CSRF, JWT, OAuth2 | spring-security-testing |
| Reactive endpoints, WebClient, SSE, R2DBC | spring-webflux-testing |
| WebSocket, STOMP messaging | spring-websocket-testing |
| AssertJ idioms, Mockito patterns, test pyramid, general Spring testing | spring-testing-fundamentals |
Slice Annotation Signals
If any of these annotations appear in the code or question, route immediately to the corresponding skill:
@DataJpaTest→spring-jpa-testing@WebMvcTest→spring-mvc-testing@WebFluxTest→spring-webflux-testing@SpringBootTest(webEnvironment = RANDOM_PORT)with STOMP →spring-websocket-testing@WithMockUser,@WithUserDetails→spring-security-testing
Default Fallback
If the domain is ambiguous and no slice annotation is visible, load spring-testing-fundamentals. It covers testing pyramid guidance, context caching, anti-patterns, and AssertJ/Mockito idioms that apply across all Spring testing scenarios.