unit-test-ddd

JUnit5 and Mockito enable automated unit testing by providing annotations for test setup, mock object creation, and assertion verification. This Skill generates JUnit5 + Mockito tests for Spring Boot domain services, entities, and repositories, following the Arrange-Act-Assert pattern with strict field validation and mock interaction verification to ensure code quality and DDD alignment.

Domain-Driven Design (DDD) testing ensures unit tests align with bounded contexts and domain logic by validating service behavior, repository interactions, and entity state changes within organized package structures. This approach prevents side effects, enforces DTO-only returns, and maintains test integrity across create, read, update, and delete operations.

Yes. This Skill automates rigorous unit test creation for DDD-structured Spring Boot applications by generating tests in app/backend/{service}/src/test/java with enforced naming conventions (test_{target}_{scenario}_{expected}), explicit field assertions, mock call verification, and exception message validation.

Strict validation in unit tests requires explicit field assertions on all DTO properties, mock interaction verification, exception message validation, and non-side-effect checks. This Skill enforces fail-fast behavior across CRUD scenarios, preventing unintended side effects and ensuring entities are never directly returned instead of DTOs.

Effective unit test naming follows the pattern test_{target}_{scenario}_{expected}, organizing tests within DDD-compliant package structures. The Arrange-Act-Assert (AAA) pattern structures each test: arrange mock dependencies, act on the service method, and assert DTO field values, mock calls, and exception messages.

Yes. This Skill generates unit tests for domain services, entities, and repositories within DDD-structured Spring Boot applications, verifying repository interactions, enforcing DTO conversion checks, and validating that no entity is directly returned from service methods.