Snippet

Validating Controller Request Payloads Using MockMvc and @WebMvcTest

`@WebMvcTest` narrows the Spring ApplicationContext down to the web layer, loading only controllers, converters, and validation logic rather than the full context. `MockMvc` provides a fluent DSL to simulate HTTP requests without starting an actual embedded web server, allowing fast verification of request body parsing, routing, and bean validation constraints.

snippet.java

java

@WebMvcTest(UserController.class)
class UserControllerTest {
 
    @Autowired
    private MockMvc mockMvc;
 
    @Test
    void shouldRejectInvalidEmail() throws Exception {
        mockMvc.perform(post("/users")
                .contentType(MediaType.APPLICATION_JSON)
                .content("{\"name\": \"Anna\", \"email\": \"invalid-email\"}"))
                .andExpect(status().isBadRequest());
    }
}

spring

Breakdown

@WebMvcTest(UserController.class)

Configures a sliced Spring context focused solely on MVC components related to `UserController`.

mockMvc.perform(post("/users")

Initiates a mock HTTP POST request targeting the `/users` endpoint.

.andExpect(status().isBadRequest());

Asserts that the controller responds with HTTP 400 Bad Request due to validation failure on the email field.

Previous snippet Next snippet

More Intermediate Java exercises →

Validating Controller Request Payloads Using MockMvc and @WebMvcTest

Related