Add conditional module: JUnit conditional test execution on 6.1.3 (JDK 25)
Fixtures for the OS, JRE, system property, environment variable and EnabledIf conditions plus a custom ExecutionCondition, run through the JUnit Platform launcher (in-process and in child JVMs) to capture real skip reasons; skipped versus aborted lifecycle; stacking, class-level skips and the deactivate switch; the 2025 article's code compiled as published; and a javap comparison of the condition package in 5.14.4 and 6.1.3. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01G8ikz8xdWuTP5yun8DZ1hk
This commit is contained in:
@@ -0,0 +1,14 @@
|
||||
Results
|
||||
a_runs() : PASSED
|
||||
b_skippedByAnnotation() : SKIPPED (Disabled on operating system: Linux)
|
||||
c_abortedByAssumption() : ABORTED (Assumption failed: database is down)
|
||||
|
||||
Every callback and test body that ran, in order
|
||||
@BeforeEach a_runs
|
||||
body a_runs
|
||||
@AfterEach a_runs
|
||||
@BeforeEach c_abortedByAssumption
|
||||
@AfterEach c_abortedByAssumption
|
||||
|
||||
The AssumptionTest from the 2025 article, unchanged
|
||||
testDatabaseConnection() : ABORTED (Assumption failed: Aborting: Database is not reachable.)
|
||||
Reference in New Issue
Block a user