RFR: 8373935: Migrate java/lang/invoke tests away from TestNG [v3]

[Jorn Vernee]

On Tue, 20 Jan 2026 23:55:02 GMT, Chen Liang <liach at openjdk.org> wrote:

>> Refactor java/lang/invoke tests to use JUnit instead of TestNG.
>> This is done by:
>> 1. First a round of automatic conversion
>> 2. Simplify exception handling tests
>> 3. Replacing `assert` keyword and switching to better assertion APIs for equality etc.
>> 4. Some other random cleanups, such as module status
>> 
>> Testing: java/lang/invoke on Linux-x64. I un-problemlisted the updated `java/lang/invoke/lambda/LambdaFileEncodingSerialization.java` too.
>
> Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 12 commits:
> 
>  - Another round of copyright year update
>  - Various bugs
>  - assertInstanceOf
>  - loop test review, test instance cleanup
>  - Use static imports
>  - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/invoke-junit
>  - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/invoke-junit
>  - Review
>  - Some omissions
>  - Whitespace
>  - ... and 2 more: https://git.openjdk.org/jdk/compare/aaca0a2c...b152f7ca

test/jdk/java/lang/invoke/MethodHandleProxies/Driver.java line 29:

> 27:  * @build m1/* m2/* Unnamed
> 28:  * @run junit/othervm m1/p1.Main
> 29:  * @run junit/othervm Unnamed

Is this still correct in combination with the changes from https://github.com/openjdk/jdk/pull/29330?

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/28879#discussion_r2721991204