ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop duplicating test methods. Learn how to use JUnit 5's @ParameterizedTest with ValueSource, CsvSource, and MethodSource to increase edge-case coverage with less code.
Learn how to use JUnit 5 @TestFactory to generate test cases at runtime. This guide covers the architectural shift from static to dynamic testing for external data sources, including lifecycle constraints and operational verification.
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.
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.
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.
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.
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.
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.
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
java