slachiewicz opened a new pull request, #235:
URL: https://github.com/apache/maven-script-interpreter/pull/235

   The four bytecode-mapping assertions were grouped in one test method, so a 
failure did not say which JDK mapping broke.
   
   - Replaced the four assertion blocks with a single `@ParameterizedTest` + 
`@CsvSource({"4, 1.4", "8, 1.8", "9, 9", "17, 17"})` method.
   - All four original mappings are still checked; `junit-jupiter-params` was 
already a test dependency.
   - `GroovyScriptInterpreterTest` surefire count 8 → 11 invocations (one 
four-assertion test became four parameterized invocations); module total 36 → 
39. No case was lost.
   
   Tracking: #14072
   
   Verified: `JAVA_HOME=<JDK 21> mvn -B -o test` → 39 tests, 0 failures/errors, 
BUILD SUCCESS (0 Checkstyle violations). Mutation: changing the `4, 1.4` row to 
`4, 1.5` fails with `expected: <1.5> but was: <1.4>`; the scratch edit was 
restored and the suite re-run green. CI not checked here (driver checks 
centrally).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to