What @SpringBootTest Does

Direct Answer

@SpringBootTest builds a Boot ApplicationContext from the selected configuration, applies the active profiles and properties, and creates the beans required by that context. It does not guarantee a production-identical environment or a connection to every external system; test configuration, mocks, disabled auto-configuration, and the chosen webEnvironment can all change what starts.

Code Example

@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
class OrderIntegrationTest {
    @Autowired private TestRestTemplate restTemplate;  // real HTTP client
    @Autowired private OrderRepository orderRepository; // real repository

    @Test
    void shouldCreateOrderEndToEnd() {
        var request = new CreateOrderRequest("Laptop", 1500.0);

        var response = restTemplate.postForEntity("/orders", request, Order.class);

        assertEquals(HttpStatus.CREATED, response.getStatusCode());
        var savedOrder = orderRepository.findById(response.getBody().getId());
        assertTrue(savedOrder.isPresent()); // verifies database persistence
    }
}

Common Mistakes & Pitfalls

• Using @SpringBootTest for isolated logic: A broad context adds setup without improving a test whose requirement is a local calculation.
• Confusing MOCK with a server: The default mode opens no HTTP port; use RANDOM_PORT or DEFINED_PORT for a client that makes real network calls.
• Assuming production equivalence: Test profiles, properties, doubles, exclusions, embedded infrastructure, and environment differences can all change behavior.