Stop Copy-Pasting Your Tests: Using JUnit 5 Parameterized Tests
Stop duplicating test methods. Learn how to use JUnit 5 @ParameterizedTest with @CsvSource and @MethodSource to decouple test logic from data and improve CI visibility.
Loading…
ReadMeFeed / Community knowledge
#junit-5
Real questions. Useful conversations. Find the people who know your stack.
Boolean Tag Expressions to Filter Cucumber Scenarios in CI
How to use boolean tag expressions and version‑aware filter config to precisely control which Cucumber scenarios run, with JUnit 5 and JUnit 4 examples.
Controlling JUnit 5 Test Execution with @Test(timeout) and Assumptions
Use JUnit 5's @Test(timeout) to fail hung or slow tests and Assume.assumeTrue/assumeFalse to skip environment-dependent tests cleanly — with verification steps and guidance on when each tool is the right choice.
junit
javaReducing Test Boilerplate with JUnit 5 Parameterized Tests
Stop writing repetitive test methods. Learn how to use JUnit 5 @ParameterizedTest to run a single test logic against multiple data sets using CsvSource and ValueSource.
JUnit 5: When to Use @ParameterizedTest Instead of Separate @Test Methods
A decision guide for JUnit 5: when @ParameterizedTest beats separate @Test methods, which data source fits your inputs, and how to verify each iteration reports individually.
Choosing Between JUnit 4 and JUnit 5 Parameterized Tests: An Architecture Note
An architecture note on JUnit parameterized tests: when the design pays off, how JUnit 4's runner differs from JUnit 5's @ParameterizedTest, and how to verify each invocation actually runs.
JUnit 5 Jupiter @Test visibility across module boundaries
In multi-module Java projects, test method visibility across module dependency boundaries determines whether non-public @Test methods are silently dropped or inadvertently exposed to consumers of compiled artifacts. JUnit 4 default runners require test methods to be public; non-public @Test methods are silently ignored unless a customized runner or rule conf
JUnit 5 Parameterized Tests and CI/CD Report Integration
Managing Test Output Volume When utilizing @ParameterizedTest in JUnit 5 (Jupiter), a single test method may execute hundreds of iterations. While the name attribute allows for descriptive identifiers, the resulting volume of successful iterations can create significant noise within CI/CD logs and XML reporting artifacts. The goal is to maintain a high level
Which JUnit 5 strategy best isolates integration tests from production credentials?
When designing an integration test suite in JUnit 5, a primary goal is to ensure that tests can execute in a CI/CD pipeline without requiring access to production API keys or sensitive credentials. While mocking external services is a common approach, it can sometimes bypass the very configuration logic the integration test is intended to verify. There is an