PluginBench
Skill
Review
Audit score 70

unit-test-controller-layer

giuseppe-trisciuoglio/developer-kit

Unit test REST controllers in isolation using MockMvc and @WebMvcTest patterns.

What is unit-test-controller-layer?

Provides patterns for unit testing Spring REST controllers with MockMvc, covering request/response mapping, validation, exception handling, and HTTP status codes. Use when testing web layer endpoints in isolation to verify API behavior without a running server.

  • Test HTTP methods (GET, POST, PUT, PATCH, DELETE) with correct status codes
  • Validate JSON responses using JsonPath assertions
  • Mock service dependencies and verify interactions
  • Test request validation and error scenarios (400, 404, 401, 403, 500)
  • Handle query parameters, path variables, and request headers
  • Test content negotiation and response headers

How to install unit-test-controller-layer

npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill unit-test-controller-layer
Prerequisites
  • Spring Boot Test starter dependency (spring-boot-starter-test)
  • Mockito for mocking service dependencies
  • JUnit 5 or JUnit 4 test framework
Claude Code
Cursor
Windsurf
Cline

How to use unit-test-controller-layer

  1. 1.Set up MockMvc using MockMvcBuilders.standaloneSetup(controller)
  2. 2.Mock all service dependencies with @Mock and inject into controller with @InjectMocks
  3. 3.Write test methods for each HTTP endpoint (GET, POST, PUT, DELETE)
  4. 4.Use mockMvc.perform() to simulate HTTP requests with parameters, headers, and body
  5. 5.Assert response status codes with status().isOk(), status().isCreated(), etc.
  6. 6.Validate response JSON using jsonPath() assertions for specific fields
  7. 7.Test error scenarios by mocking service exceptions and verifying error status codes
  8. 8.Verify mock service method calls using verify(service).method(args)

Use cases

Good for
  • Verify REST API endpoints return correct status codes and response bodies
  • Test validation error handling and error message formatting
  • Validate authorization headers and security constraints
  • Test content negotiation with different Accept/Content-Type headers
  • Verify mock service interactions and method call counts
Who it's for
  • Spring Boot developers writing controller unit tests
  • Backend engineers testing REST API endpoints
  • QA engineers automating API contract validation
  • Teams practicing test-driven development for web layers

unit-test-controller-layer FAQ

Should I use standaloneSetup() or webApplicationContext?

Use standaloneSetup() for isolated controller unit tests. Use webApplicationContext for integration tests that need full Spring context, validators, and interceptors.

How do I test @PreAuthorize or @Secured annotations?

standaloneSetup() does not support security annotations by default. Either use webApplicationContext for full context, or test authorization logic separately in a dedicated security test class.

How do I test file uploads?

Use MockMultipartFile to simulate multipart requests: mockMvc.perform(multipart("/upload").file(new MockMultipartFile(...)))

Can I test response headers?

Yes, use .andExpect(header().exists("X-Header-Name")) or .andExpect(header().string("X-Header-Name", "value")) to assert response headers.

What if my test fails with JsonPath assertion errors?

Add .andDo(print()) before assertions to see the actual response body, then adjust your jsonPath() expression to match the actual JSON structure.

Full instructions (SKILL.md)

Source of truth, from giuseppe-trisciuoglio/developer-kit.


name: unit-test-controller-layer description: Provides patterns for unit testing REST controllers using MockMvc and @WebMvcTest. Generates controller tests that validates request/response mapping, validation, exception handling, and HTTP status codes. Use when testing web layer endpoints in isolation for API endpoint testing, Spring MVC tests, mock HTTP requests, or controller layer unit tests. allowed-tools: Read, Write, Bash, Glob, Grep

Unit Testing REST Controllers with MockMvc

Overview

Provides patterns for unit testing @RestController and @Controller classes using MockMvc. Covers request/response handling, HTTP status codes, request parameter binding, validation, content negotiation, response headers, and exception handling with mocked service dependencies.

When to Use

Use for: controller tests, API endpoint testing, Spring MVC tests, mock HTTP requests, unit testing web layer endpoints, verifying REST controllers in isolation.

Instructions

  1. Setup standalone MockMvc: MockMvcBuilders.standaloneSetup(controller) for isolated testing
  2. Mock service dependencies: Use @Mock for all services, @InjectMocks for the controller
  3. Test HTTP methods: GET, POST, PUT, PATCH, DELETE with correct status codes
  4. Validate responses: JsonPath assertions for JSON, content matchers for body
  5. Test validation: Send invalid input, verify 400 status with error details
  6. Test errors: Verify 404, 400, 401, 403, 500 for appropriate conditions
  7. Validate headers: Both request (Authorization) and response headers
  8. Test content negotiation: Different Accept and Content-Type headers

Validation Workflow

Run test → If fails: add .andDo(print()) → Check actual vs expected → Fix assertion

Examples

Maven / Gradle Dependencies

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-test</artifactId>
  <scope>test</scope>
</dependency>

Basic Pattern: GET Endpoint

import static org.mockito.Mockito.*;
import static org.springframework.test.web.servlet.request.MockMvcRequestBuilders.*;
import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.*;

@ExtendWith(MockitoExtension.class)
class UserControllerTest {

  @Mock
  private UserService userService;

  @InjectMocks
  private UserController userController;

  private MockMvc mockMvc;

  @BeforeEach
  void setUp() {
    mockMvc = MockMvcBuilders.standaloneSetup(userController).build();
  }

  @Test
  void shouldReturnAllUsers() throws Exception {
    List<UserDto> users = List.of(new UserDto(1L, "Alice"), new UserDto(2L, "Bob"));
    when(userService.getAllUsers()).thenReturn(users);

    mockMvc.perform(get("/api/users"))
      .andExpect(status().isOk())
      .andExpect(jsonPath("$[0].id").value(1))
      .andExpect(jsonPath("$[0].name").value("Alice"));

    verify(userService, times(1)).getAllUsers();
  }

  @Test
  void shouldReturn404WhenUserNotFound() throws Exception {
    when(userService.getUserById(999L))
      .thenThrow(new UserNotFoundException("User not found"));

    mockMvc.perform(get("/api/users/999"))
      .andExpect(status().isNotFound());

    verify(userService).getUserById(999L);
  }
}

POST: Create Resource

@Test
void shouldCreateUserAndReturn201() throws Exception {
  UserDto createdUser = new UserDto(1L, "Alice", "alice@example.com");
  when(userService.createUser(any())).thenReturn(createdUser);

  mockMvc.perform(post("/api/users")
      .contentType("application/json")
      .content("{\"name\":\"Alice\",\"email\":\"alice@example.com\"}"))
    .andExpect(status().isCreated())
    .andExpect(jsonPath("$.id").value(1))
    .andExpect(jsonPath("$.name").value("Alice"));

  verify(userService).createUser(any(UserCreateRequest.class));
}

PUT: Update Resource

@Test
void shouldUpdateUserAndReturn200() throws Exception {
  UserDto updatedUser = new UserDto(1L, "Updated");
  when(userService.updateUser(eq(1L), any())).thenReturn(updatedUser);

  mockMvc.perform(put("/api/users/1")
      .contentType("application/json")
      .content("{\"name\":\"Updated\"}"))
    .andExpect(status().isOk())
    .andExpect(jsonPath("$.name").value("Updated"));

  verify(userService).updateUser(eq(1L), any());
}

DELETE: Remove Resource

@Test
void shouldDeleteUserAndReturn204() throws Exception {
  doNothing().when(userService).deleteUser(1L);

  mockMvc.perform(delete("/api/users/1"))
    .andExpect(status().isNoContent());

  verify(userService).deleteUser(1L);
}

Query Parameters

@Test
void shouldFilterUsersByName() throws Exception {
  when(userService.searchUsers("Alice")).thenReturn(List.of(new UserDto(1L, "Alice")));

  mockMvc.perform(get("/api/users/search").param("name", "Alice"))
    .andExpect(status().isOk())
    .andExpect(jsonPath("$[0].name").value("Alice"));

  verify(userService).searchUsers("Alice");
}

Path Variables

@Test
void shouldGetUserByIdFromPath() throws Exception {
  when(userService.getUserById(123L)).thenReturn(new UserDto(123L, "Alice"));

  mockMvc.perform(get("/api/users/{id}", 123L))
    .andExpect(status().isOk())
    .andExpect(jsonPath("$.id").value(123));
}

Validation Errors (400)

@Test
void shouldReturn400WhenRequestBodyInvalid() throws Exception {
  mockMvc.perform(post("/api/users")
      .contentType("application/json")
      .content("{\"name\":\"\"}"))
    .andExpect(status().isBadRequest())
    .andExpect(jsonPath("$.errors").isArray());
}

Response Headers

@Test
void shouldReturnCustomHeaders() throws Exception {
  when(userService.getAllUsers()).thenReturn(List.of());

  mockMvc.perform(get("/api/users"))
    .andExpect(status().isOk())
    .andExpect(header().exists("X-Total-Count"))
    .andExpect(header().string("X-Total-Count", "0"));
}

Authorization Header

@Test
void shouldRequireAuthorizationHeader() throws Exception {
  mockMvc.perform(get("/api/users"))
    .andExpect(status().isUnauthorized());

  mockMvc.perform(get("/api/users").header("Authorization", "Bearer token"))
    .andExpect(status().isOk());
}

Content Negotiation

@Test
void shouldReturnJsonWhenAcceptHeaderIsJson() throws Exception {
  when(userService.getUserById(1L)).thenReturn(new UserDto(1L, "Alice"));

  mockMvc.perform(get("/api/users/1").accept("application/json"))
    .andExpect(status().isOk())
    .andExpect(content().contentType("application/json"));
}

Best Practices

  • Use standaloneSetup() for isolated controller testing
  • Mock service layer — controllers handle HTTP, services handle business logic
  • Verify mock interactions: verify(service).method(args)
  • Test happy path AND error scenarios (404, 400, 500)
  • Use jsonPath() for fluent JSON assertions
  • One focused assertion per test method

Constraints and Warnings

  • Controller tests verify HTTP handling only — not full request flow
  • standaloneSetup() may not support @Validated without full context
  • JsonPath requires valid JSON in response body
  • @PreAuthorize/@Secured need additional setup — consider separate security tests
  • File uploads require MockMultipartFile

References