Skip to main content
unit-test-bean-validation Provides patterns for unit testing Jakarta Bean Validation (JSR-380), including @Valid, @NotNull, @Min, @Max, @Email constraints with Hibernate Validator. Generates custom validator tests, constraint violation assertions, validation groups, and parameterized validation tests. Validates data integrity logic without Spring context. Use when writing validation tests, bean validation tests, or testing custom constraint validators.
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill unit-test-bean-validationLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Métiers associés SOC
Basé sur la classification professionnelle SOC
Explorateur de fichiers
3 fichiers name unit-test-bean-validation description Provides patterns for unit testing Jakarta Bean Validation (JSR-380), including @Valid, @NotNull, @Min, @Max, @Email constraints with Hibernate Validator. Generates custom validator tests, constraint violation assertions, validation groups, and parameterized validation tests. Validates data integrity logic without Spring context. Use when writing validation tests, bean validation tests, or testing custom constraint validators. allowed-tools Read, Write, Bash, Glob, Grep
Unit Testing Jakarta Bean Validation
Overview
This skill provides executable patterns for unit testing Jakarta Bean Validation annotations and custom validators using JUnit 5. Covers built-in constraints (@NotNull, @Email, @Min, @Max, @Size), custom @Constraint implementations, cross-field validation, and validation groups. Tests run in isolation without Spring context.
When to Use
Writing unit tests for Jakarta Bean Validation or JSR-380 constraints
Testing custom @Constraint validators and constraint violation messages
Testing bean validation logic in DTOs and request objects
Verifying cross-field validation (e.g., password matching)
Testing conditional validation with validation groups
Fast validation tests without Spring Boot context
Instructions
Add dependencies : Include jakarta.validation-api and hibernate-validator in test scopeCreate base test class : Build
Validator
@BeforeEach
Validation.buildDefaultValidatorFactory()
Test valid cases first : Verify objects pass without violations
Test invalid cases : Assert constraint violations include correct property path and message
Extract violation details : Use getPropertyPath(), getMessage(), getInvalidValue()
Test custom validators : See references/custom-validators.md for patterns
Use parameterized tests : Test multiple inputs efficiently with @ParameterizedTest
Group validation tests : Use validation groups for conditional rules (see references/advanced-patterns.md)
Examples
Maven Setup <dependency >
<groupId > jakarta.validation</groupId >
<artifactId > jakarta.validation-api</artifactId >
</dependency >
<dependency >
<groupId > org.hibernate.validator</groupId >
<artifactId > hibernate-validator</artifactId >
<scope > test</scope >
</dependency >
<dependency >
<groupId > org.assertj</groupId >
<artifactId > assertj-core</artifactId >
<scope > test</scope >
</dependency >
Common Test Setup import jakarta.validation.*;
import jakarta.validation.ConstraintViolation;
import jakarta.validation.path.Path;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.assertj.core.api.Assertions.*;
class BaseValidationTest {
protected Validator validator;
@BeforeEach
void setUpValidator () {
validator = Validation.buildDefaultValidatorFactory().getValidator();
}
}
Testing Basic Constraints class UserDtoTest extends BaseValidationTest {
@Test
void shouldPassValidationWithValidUser () {
UserDto user = new UserDto ("Alice" , "alice@example.com" , 25 );
assertThat(validator.validate(user)).isEmpty();
}
@Test
void shouldFailWhenNameIsNull () {
UserDto user = new UserDto (null , "alice@example.com" , 25 );
assertThat(validator.validate(user))
.extracting(ConstraintViolation::getMessage)
.contains("must not be blank" );
}
@Test
void shouldFailWhenEmailIsInvalid () {
UserDto user = new UserDto ("Alice" , "invalid-email" , 25 );
Set<ConstraintViolation<UserDto>> violations = validator.validate(user);
assertThat(violations)
.extracting(ConstraintViolation::getPropertyPath)
.extracting(Path::toString)
.contains("email" );
}
@Test
void shouldFailWhenAgeIsBelowMinimum () {
UserDto user = new UserDto ("Alice" , "alice@example.com" , -1 );
assertThat(validator.validate(user))
.extracting(ConstraintViolation::getMessage)
.contains("must be greater than or equal to 0" );
}
@Test
void shouldFailWhenMultipleConstraintsViolated () {
UserDto user = new UserDto (null , "invalid" , -5 );
assertThat(validator.validate(user)).hasSize(3 );
}
}
Testing Custom Validators For custom constraint patterns, see references/custom-validators.md:
Creating @Constraint annotations
Implementing ConstraintValidator
Cross-field validation (password matching)
Stateless validator best practices
Testing Validation Groups For validation groups and parameterized tests, see references/advanced-patterns.md:
Defining validation group interfaces
Conditional validation with groups parameter
@ParameterizedTest with @ValueSource and @CsvSourceDebugging failed validation tests
Best Practices
Test both valid and invalid : Every constraint needs both passing and failing test casesAssert violation details : Verify property path, message, and constraint typeTest edge cases : null, empty string, whitespace-only, boundary valuesKeep validators stateless : Custom validators must not maintain stateUse clear messages : Constraint messages should be user-friendlyGroup related tests : Extend BaseValidationTest to share validator setupTest error messages : Ensure messages match requirements
Common Pitfalls
Forgetting to test null values (most constraints ignore null by default)
Not verifying the property path in constraint violations
Testing validation at service/controller level instead of unit level
Creating overly complex custom validators
Missing @NotNull for mandatory fields combined with other constraints
Constraints and Warnings
Null handling : Most constraints ignore null by default — combine @NotNull with other constraints for mandatory fieldsThread safety : Validator instances are thread-safe and can be sharedMessage localization : Test with different locales if i18n is requiredCascading validation : Use @Valid on nested objects for recursive validationCustom validators : Must be stateless and return true for null valuesTest isolation : Validation unit tests should not depend on Spring context or database
Troubleshooting ValidatorFactory not found : Ensure jakarta.validation-api and hibernate-validator are on test classpath.
Custom validator not invoked : Verify @Constraint(validatedBy = YourValidator.class) annotation is correct.
Null values pass validation : This is expected behavior — constraints ignore null unless @NotNull is present.
Wrong violation count : Use hasSize() to verify exact count, check all fields in the object.
Property path incorrect : Ensure the field, not the getter, has the constraint annotation.
References Plus depuis ce dépôt Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them published on a PR as inline review comments. Triggers include "post these review comments on the PR", "associate comments to files in the PR", "publish review findings to PR
typescript-security-review Provides security review capability for TypeScript/Node.js applications, validates code against XSS, injection, CSRF, JWT/OAuth2 flaws, dependency CVEs, and secrets exposure. Use when performing security audits, before deployment, reviewing authentication/authorization implementations, or ensuring OWASP compliance for Express, NestJS, and Next.js. Triggers on "security review", "check for security issues", "TypeScript security audit".
Initialize Spec-Driven Development context — detects tech stack, conventions, architecture patterns, and bootstraps persistence backends. Triggers on 'sdd-init', 'init sdd', 'setup sdd', 'initialize sdd', 'setup project', 'initialize project context'. Creates/updates docs/specs/architecture.md & ontology.md (Constitution), and populates knowledge-graph.json.
