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.
Loading…
ReadMeFeed / Community knowledge
#junit-5
Real questions. Useful conversations. Find the people who know your stack.
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.
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 default lifecycle requires static @BeforeAll and @AfterAll
A JUnit 5 test class requires non-static @BeforeAll and @AfterAll methods so setup can use constructor-injected dependencies. Under the default lifecycle, JUnit 5 instantiates the test class once per test method and rejects non-static class-level lifecycle methods. Enabling @TestInstance(TestInstance.Lifecycle.PER_CLASS) reuses a single instance for all test
JUnit 5: Unclear Interaction of @RepeatedTest with @ParameterizedTest
Unresolved Decision: @RepeatedTest and @ParameterizedTest The goal is to determine how JUnit 5 executes tests when a @RepeatedTest annotation is combined with a @ParameterizedTest . The current specification does not state whether the repetitions apply to each individual parameter set or to the entire parameterized sequence, leading to ambiguous execution or