Discussed in the PAG meeting of 2024-09-12; I need to do this sooner rather than later, for now I only have 12 of those tests in flight, but this is growing rapidly.
Also make it explicit which characters are having their properties tested and which ones are just property values in the Propertywise/CorrespondTo tests (this makes it much easier to test numerals, since I can then use ASCII digits as value-only « ⧴ » counterparts for Numeric_Value.
This should also make it nicer to check coverage; for some of those tests it can be unclear whether there are gaps of characters whose properties are not tested; in such cases one could have some sort of declaration that « this tests the properties of U+XXXX...U+YYYY » at the top of the file, and it would be easy to check that all those characters show up in a Propertywise/AreAlike test or before the first ⧴ in a Propertywise/CorrespondTo test.
Discussed in the PAG meeting of 2024-09-12; I need to do this sooner rather than later, for now I only have 12 of those tests in flight, but this is growing rapidly.
Also make it explicit which characters are having their properties tested and which ones are just property values in the Propertywise/CorrespondTo tests (this makes it much easier to test numerals, since I can then use ASCII digits as value-only « ⧴ » counterparts for Numeric_Value. This should also make it nicer to check coverage; for some of those tests it can be unclear whether there are gaps of characters whose properties are not tested; in such cases one could have some sort of declaration that « this tests the properties of U+XXXX...U+YYYY » at the top of the file, and it would be easy to check that all those characters show up in a Propertywise/AreAlike test or before the first ⧴ in a Propertywise/CorrespondTo test.