What problem does it solve? Writing Spring Boot component (slice) tests is error-prone: developers must boot the full application context, replace external collaborators with deterministic fakes, disable security correctly, and cover every HTTP status branch. This Skill provides a proven structure, configuration patterns, and ready-to-fill templates so component tests are consistent and fast. ## Core Features & Use Cases - Standardized test layout: Defines a canonical structure with ComponentTestConfiguration, opt-out configs for heavy startup beans, and a shared TestsResourcesHolder for fixtures. - Deterministic test doubles: Guides replacing HTTP clients, file stores, and permission handlers with @Primary mocks that branch on input, avoiding slow context restarts from @MockBean. - Full contract coverage: Enforces testing all HTTP status branches (2xx, 4xx, 5xx) through the real HTTP API using TestRestTemplate or MockMvc with JsonPath assertions. - Use Case: When adding a new REST endpoint to a Spring Boot microservice, generate a component test class that boots the app on a random port, fakes its downstream dependencies, and verifies the endpoint's contract end-to-end. ## Quick Start Ask the AI to apply the component-tests skill to generate a component test for your new REST controller endpoint.