Skip to main content
skill CX Codex

unit-test-mapper-converter — Claude Code skill: mapper unit tests

A skill for unit-testing MapStruct mappers and converters: field mapping, null handling, nested objects and round-trip conversion.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-mapper-converter -a claude-code
Open on GitHub

What unit-test-mapper-converter does

The skill lays out test patterns for MapStruct mappers and custom converter classes. It covers field mapping accuracy, null handling, type conversions, nested object mapping, bidirectional mapping, enum mapping and partial updates. Inside are ready examples on JUnit 5 and AssertJ, including a complete test class with imports.

Before running tests, the skill tells you to check that generated mapper classes exist: ls target/generated-sources/ for Maven or ls build/generated/sources/ for Gradle. If they are missing, run mvn compile or ./gradlew compileJava. MapStruct generates code at compile time, so without that step the tests will not find the classes. One more catch: expressions in @Mapping(target = "field", expression = "java(...)") are not validated at compile time, so they need explicit tests.

The skill uses Read, Write, Bash, Glob and Grep. Standalone tests rely on Mappers.getMapper(), integration tests on Spring injection. MapStruct limits get their own section: circular dependencies between mappers are not supported, immutable collections may need extra configuration, and date/time objects are worth checking across timezones.

What it helps with

  • write unit tests for a MapStruct mapper
  • check null handling when converting entity to DTO
  • test bidirectional mapping and catch asymmetries
  • cover nested objects and collection transformations
  • verify enum mapping through @ValueMapping

Example prompts for the agent

  • Write tests for UserMapper covering null input and round-trip mapping
  • Generate unit tests for the OrderEntity to OrderDto converter
  • Check that nested object mapping works with usingRecursiveComparison

How to install unit-test-mapper-converter

1Skills CLI (Vercel)

npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-mapper-converter -a claude-code

2Manually: put the files in place

~/.claude/skills/unit-test-mapper-converter/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/unit-test-mapper-converter/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about unit-test-mapper-converter

How do I install unit-test-mapper-converter in Claude?

Run npx skills add giuseppe-trisciuoglio/developer-kit --skill unit-test-mapper-converter -a claude-code. The skill lands in ~/.claude/skills/unit-test-mapper-converter/SKILL.md.

What does unit-test-mapper-converter do?

It provides patterns for unit-testing MapStruct mappers and custom converters: field mapping, null handling, nested objects, enums, partial updates. It generates executable tests with JUnit 5 and AssertJ.

What MapStruct limits does the skill warn about?

Circular dependencies between mappers are not supported. Expressions in @Mapping are not validated at compile time, and immutable collections may need special configuration.

Source text

SKILL.md · MIT
---
name: unit-test-mapper-converter
description: Provides patterns for unit testing mappers, converters, and bean mappings. Validates entity-to-DTO and model transformation logic in isolation. Generates executable mapping tests with MapStruct and custom converter test coverage. Use when writing mapping tests, converter tests, entity mapping tests, or ensuring correct data transformation between DTOs and domain objects.
allowed-tools: Read, Write, Bash, Glob, Grep
---

# Unit Testing Mappers and Converters

## Overview

Provides patterns for unit testing MapStruct mappers and custom converter classes. Covers field mapping accuracy, null handling, type conversions, nested object transformations, bidirectional mapping, enum mapping, and partial updates.

## When to Use

- Writing mapping tests for MapStruct mapper implementations
- Testing custom entity-to-DTO converters and bean mappings
- Validating nested object mapping and collection transformations

## Instructions

### 1. Validate Generated Mapper Classes
Before testing, verify generated mapper classes exist:
```bash
# Maven
ls target/generated-sources/

# Gradle
ls build/generated/sources/
```

**If generated classes are missing:**
1. Run `mvn compile` (Maven) or `./gradlew compileJava` (Gradle)
2. Check that the MapStruct annotation processor is configured
3. Verify `@Mapper` interfaces are in a compiled source set

### 2. Test Null Handling
```java
assertThat(mapper.toDto(null)).isNull();
```
Configure `nullValueMappingStrategy` in mapper if null should return empty/default.

**If null tests fail:**
1. Add `nullValueMappingStrategy = NullValueMappingStrategy.RETURN_NULL` to `@Mapper`
2. Or use `nullValuePropertyMappingStrategy` for nested property handling

### 3. Test Bidirectional Mapping
```java
User restored = mapper.toEntity(mapper.toDto(original));
assertThat(restored).usingRecursiveComparison().isEqualTo(original);
```

**If bidirectional tests fail:**
1. Check `@Mapping` annotations for field name mismatches
2. Verify both directions are explicitly mapped if auto-mapping fails
3. Use `unmappedTargetPolicy = ReportingPolicy.ERROR` to catch missing mappings

### 4. Test Nested Object Mapping
```java
assertThat(dto.getNested()).usingRecursiveComparison().isEqualTo(expected);
```

**If nested tests fail:**
1. Ensure nested mapper exists or is referenced via `uses = NestedMapper.class`
2. Check collection element mappings with `elementMappingStrategy`

### 5. Test Custom Expressions
Custom expressions in `@Mapping(target = "field", expression = "java(...)")` are not compile-time validated.

**If expression tests fail:**
1. Verify the expression syntax and method signatures
2. Check that imported classes are accessible from the expression context

### 6. Test Enum Mappings
Use `@ValueMapping` for enum-to-enum translations. Test all enum values exhaustively.

## Best Practices

- Use `Mappers.getMapper()` for standalone tests, Spring injection for integration tests
- Use `usingRecursiveComparison()` for complex nested structures
- Test all mapper methods including collection transformations
- Verify null handling for all nullable source fields
- Test bidirectional mapping catches asymmetries between entity→DTO and DTO→entity
- Keep mapper tests focused on transformation correctness, not implementation details

## Constraints and Warnings

- **Compile-time generation**: MapStruct generates code at compile time—verify generated classes exist before running tests
- **Null handling**: Configure `nullValueMappingStrategy` and `nullValuePropertyMappingStrategy` appropriately
- **Expression validation**: Expressions in `@Mapping` are not validated at compile time—test them explicitly
- **Circular dependencies**: MapStruct cannot handle circular dependencies between mappers
- **Collection immutability**: Mapping immutable collections may require special configuration
- **Date/Time**: Verify date/time objects map correctly across timezones

## Examples

Complete executable test with imports:
```java
package com.example.mapper;

import org.junit.jupiter.api.Test;
import org.mapstruct.factory.Mappers;
import static org.assertj.core.api.Assertions.*;

class UserMapperCompleteTest {
  private final UserMapper mapper = Mappers.getMapper(UserMapper.class);

  @Test
  void shouldMapUserToDto() {
    User user = new User(1L, "Alice", "[email protected]", 25);
    UserDto dto = mapper.toDto(user);
    assertThat(dto)
      .isNotNull()
      .extracting(UserDto::getName, UserDto::getEmail)
      .containsExactly("Alice", "[email protected]");
  }

  @Test
  void shouldMaintainRoundTrip() {
    User original = new User(1L, "Alice", "[email protected]", 25);
    assertThat(mapper.toEntity(mapper.toDto(original)))
      .usingRecursiveComparison()
      .isEqualTo(original);
  }

  @Test
  void shouldHandleNullInput() {
    assertThat(mapper.toDto(null)).isNull();
  }
}
```

Additional examples in: `references/examples.md`

© giuseppe-trisciuoglio · MIT · giuseppe-trisciuoglio/developer-kit

Similar skills

All skills for Testing and QA →

From the same set96

unit-test-config-properties Provides JUnit 5 patterns to unit test Spring Boot @ConfigurationProperties using ApplicationContextRunner without starting a full application context. CX Codex +1 3,700installs unit-test-caching Unit test patterns for Spring Cache annotations: cache hits and misses, eviction, SpEL keys, all without booting a full Spring context. CX Codex +1 3,700installs langchain4j-ai-services-patterns A skill that walks your agent through declarative AI Services in LangChain4j: interfaces, annotations, memory and tool calling. CX Codex +1 3,700installs qdrant Provides integration patterns for the Qdrant vector database in Java and Spring Boot with LangChain4j. Helps build semantic search and vector stores for RAG. CX Codex +1 3,700installs unit-test-exception-handler Patterns for unit testing @ExceptionHandler and @ControllerAdvice in Spring Boot: status codes, JSON error bodies and field-level validation errors. CX Codex +1 3,700installs rag Guides the creation of Retrieval-Augmented Generation pipelines, covering document chunking, embedding generation, vector database selection, and retrieval. CX Codex +1 3,700installs unit-test-scheduled-async A skill with ready patterns for unit testing Spring @Scheduled and @Async methods: JUnit 5, CompletableFuture, Awaitility, Mockito. CX Codex +1 3,700installs unit-test-utility-methods Writes unit tests for utility classes and static methods, covering nulls, empty input, boundaries and floating-point precision. CX Codex +1 3,700installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor