This is an umbrella issue tracking the progress of converting JUnit 3, JUnit 4, and TestNG-based test to using JUnit Jupiter API (aka JUnit 5).
The following command prints an overview of how many tests are using the "testng" runner via the jtreg syntax:
find test/* -name \*.java | xargs grep '@run' | grep testng | grep "java:" | cut -d : -f 1 | cut -d / -f 1-3 | sort | uniq -c | sort -nr
It will show something similar to
```
1299 test/jdk/java
891 test/jaxp/javax
151 test/jdk/jdk
138 test/hotspot/jtreg
101 test/langtools/jdk
65 test/langtools/tools
62 test/jdk/sun
54 test/jdk/tools
39 test/jdk/com
25 test/jdk/sanity
14 test/jdk/javax
5 test/lib-test/jdk
```
Dedicated sub-tasks will be created for components/groups.
The following command prints an overview of how many tests are using the "testng" runner via the jtreg syntax:
find test/* -name \*.java | xargs grep '@run' | grep testng | grep "java:" | cut -d : -f 1 | cut -d / -f 1-3 | sort | uniq -c | sort -nr
It will show something similar to
```
1299 test/jdk/java
891 test/jaxp/javax
151 test/jdk/jdk
138 test/hotspot/jtreg
101 test/langtools/jdk
65 test/langtools/tools
62 test/jdk/sun
54 test/jdk/tools
39 test/jdk/com
25 test/jdk/sanity
14 test/jdk/javax
5 test/lib-test/jdk
```
Dedicated sub-tasks will be created for components/groups.