Skip to main content
unit-test-parameterized Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value analysis.
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-parameterizedLa 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... 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.
Métiers associés SOC
Basé sur la classification professionnelle SOC
name unit-test-parameterized description Provides parameterized testing patterns with JUnit 5, generates data-driven unit tests using @ParameterizedTest, @ValueSource, @CsvSource, @MethodSource. Creates tests that run the same logic with multiple input values. Use when writing data-driven Java tests, multiple test cases from single method, or boundary value analysis. allowed-tools Read, Write, Bash, Glob, Grep
Parameterized Unit Tests with JUnit 5
Overview
Provides patterns for parameterized unit tests in Java using JUnit 5. Covers @ValueSource, @CsvSource, @MethodSource, @EnumSource, @ArgumentsSource, and custom display names. Reduces test duplication by running the same test logic with multiple input values.
When to Use
Writing JUnit tests with multiple input combinations
Implementing data-driven tests in Java
Running same test with different values (boundary analysis)
Testing multiple scenarios from single test method
Instructions
Add dependency : Ensure junit-jupiter-params is on test classpath (included in junit-jupiter)Choose source : @ValueSource for simple values, @CsvSource for tabular data, @MethodSource for complex objectsMatch parameters : Test method parameters must match data source typesSet display names : Use name = "{0}..." for readable output
Validate : Run ./gradlew test --info or mvn test and verify all parameter combinations execute
Examples
Maven / Gradle Dependency JUnit 5 parameterized tests require junit-jupiter (includes params). Add assertj-core for assertions:
<dependency >
<groupId > org.junit.jupiter</groupId >
<artifactId > junit-jupiter</artifactId >
<scope > test</scope >
</dependency >
testImplementation("org.junit.jupiter:junit-jupiter" )
@ValueSource — Simple Valuesimport org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;
import static org.assertj.core.api.Assertions.*;
@ParameterizedTest
@ValueSource(strings = {"hello", "world", "test"})
void shouldCapitalizeAllStrings (String input) {
assertThat(StringUtils.capitalize(input)).isNotEmpty();
}
@ParameterizedTest
@ValueSource(ints = {1, 2, 3, 4, 5})
void shouldBePositive (int number) {
assertThat(number).isPositive();
}
@ParameterizedTest
@ValueSource(ints = {Integer.MIN_VALUE, -1, 0, 1, Integer.MAX_VALUE})
void shouldHandleBoundaryValues (int value) {
assertThat(Math.incrementExact(value)).isGreaterThan(value);
}
@CsvSource — Tabular Dataimport org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.CsvSource;
@ParameterizedTest
@CsvSource({
"alice@example.com, true",
"bob@gmail.com, true",
"invalid-email, false",
"user@, false",
"@example.com, false"
})
void shouldValidateEmailAddresses (String email, boolean expected) {
assertThat(UserValidator.isValidEmail(email)).isEqualTo(expected);
}
@MethodSource — Complex Dataimport org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.MethodSource;
import java.util.stream.Stream;
@ParameterizedTest
@MethodSource("additionTestCases")
void shouldAddNumbersCorrectly (int a, int b, int expected) {
assertThat(Calculator.add(a, b)).isEqualTo(expected);
}
static Stream<Arguments> additionTestCases () {
return Stream.of(
Arguments.of(1 , 2 , 3 ),
Arguments.of(0 , 0 , 0 ),
Arguments.of(-1 , 1 , 0 ),
Arguments.of(100 , 200 , 300 )
);
}
@EnumSource — Enum Values@ParameterizedTest
@EnumSource(Status.class)
void shouldHandleAllStatuses (Status status) {
assertThat(status).isNotNull();
}
@ParameterizedTest
@EnumSource(value = Status.class, names = {"ACTIVE", "INACTIVE"})
void shouldHandleSpecificStatuses (Status status) {
assertThat(status).isIn(Status.ACTIVE, Status.INACTIVE);
}
Custom Display Names @ParameterizedTest(name = "Discount of {0}% should be calculated correctly")
@ValueSource(ints = {5, 10, 15, 20})
void shouldApplyDiscount (int discountPercent) {
double result = DiscountCalculator.apply(100.0 , discountPercent);
assertThat(result).isEqualTo(100.0 * (1 - discountPercent / 100.0 ));
}
Custom ArgumentsProvider class RangeValidatorProvider implements ArgumentsProvider {
@Override
public Stream<? extends Arguments > provideArguments(ExtensionContext context) {
return Stream.of(
Arguments.of(0 , 0 , 100 , true ),
Arguments.of(50 , 0 , 100 , true ),
Arguments.of(-1 , 0 , 100 , false ),
Arguments.of(101 , 0 , 100 , false )
);
}
}
@ParameterizedTest
@ArgumentsSource(RangeValidatorProvider.class)
void shouldValidateRange (int value, int min, int max, boolean expected) {
assertThat(RangeValidator.isInRange(value, min, max)).isEqualTo(expected);
}
Error Condition Testing @ParameterizedTest
@ValueSource(strings = {"", " ", null})
void shouldThrowExceptionForInvalidInput (String input) {
assertThatThrownBy(() -> Parser.parse(input))
.isInstanceOf(IllegalArgumentException.class);
}
Best Practices
Use descriptive display names: name = "{0}..." for readable output
Test boundary values: include min, max, zero, and edge cases
Keep test logic focused: single assertion per parameter set
Use @MethodSource for complex objects, @CsvSource for tabular data
Organize test data logically — group related scenarios together
Constraints and Warnings
Parameter count must match : Number of parameters from source must match test method signature@ValueSource limitationCSV escaping : Strings with commas must use single quotes in @CsvSource@MethodSource visibilityDisplay name placeholders : Use {0}, {1}, etc. to reference parametersExecution count : Each parameter set runs as a separate test invocation
References 