This test improvements were suggested by Igor during the review of "Test plan for JDK-8072061 - Automatically determine optimal sizes for the CDS regions".
Here are the suggested boundary cases:
1) class list w/ only one unverifiable class
2) class list w/ N unverifiable class
3) class list w/ N unverifiable class and M verifiable class
and if it hasn't been covered by existing tests:
4) empty class list
5) class list w/ 1 verifiable class
6) class list w/ M verifiable class
NOTE: Some of these test cases may already exist within CDS or AppCDS tests. So first check if they exist. If they do, list the test name and test case for each number. For the cases that do not exist implement them where applicable (either modify existing test, or add a new one).
Here are the suggested boundary cases:
1) class list w/ only one unverifiable class
2) class list w/ N unverifiable class
3) class list w/ N unverifiable class and M verifiable class
and if it hasn't been covered by existing tests:
4) empty class list
5) class list w/ 1 verifiable class
6) class list w/ M verifiable class
NOTE: Some of these test cases may already exist within CDS or AppCDS tests. So first check if they exist. If they do, list the test name and test case for each number. For the cases that do not exist implement them where applicable (either modify existing test, or add a new one).