Snippet

Verifying Custom Controller Advice Responses with MockMvc and JSON Path

Integration slice testing with @WebMvcTest validates that business exceptions thrown from service layers are correctly translated into RFC 7807 problem details or custom error structures by @ExceptionHandler methods.

snippet.java

java

@WebMvcTest(OrderController.class)
class OrderControllerTest {
    @Autowired
    private MockMvc mockMvc;
    @MockBean
    private OrderService orderService;
 
    @Test
    void shouldReturnNotFoundProblemDetails() throws Exception {
        Mockito.when(orderService.getOrder(404L))
               .thenThrow(new EntityNotFoundException("Order 404 not found"));
 
        mockMvc.perform(MockMvcRequestBuilders.get("/api/orders/404"))
               .andExpect(MockMvcResultMatchers.status().isNotFound())
               .andExpect(MockMvcResultMatchers.jsonPath("$.detail").value("Order 404 not found"));
    }
}

spring

Breakdown

@WebMvcTest(OrderController.class)

Focuses the test context exclusively on the MVC layer, configuring MockMvc and controller advice.

Mockito.when(orderService.getOrder(404L)).thenThrow(new EntityNotFoundException("Order 404 not found"));

Simulates a failure condition in the mocked service layer.

.andExpect(MockMvcResultMatchers.jsonPath("$.detail").value("Order 404 not found"));

Uses JSONPath syntax to assert the serialized structure of the error payload.

Previous snippet Next snippet

More Intermediate Java exercises →

Verifying Custom Controller Advice Responses with MockMvc and JSON Path

Related