CSS 2.1 test suite feedback: organizational

I've been through about 60% of the HTML4 tests in the 20100917 suite, and have some feedback.

This message is about the organization of the suite as a whole. I realize that some of these suggestions come too late to be applied to the 2.1 suite, but hope that we can apply then to future test suites.

For pure cleanliness reasons, I suggest that the files in the html4 and xhtml1 directories are broken into test files and non-test files. I suggest a hierarchy like the following:


It would be very helpful if testinfo.data file had the following additional columns, to allow a test harness to categorize and present tests in the same order that they are presented in chapters:

chapters: comma-separated list of chapters that the test is applicable to (e.g. "3, 4, E").
indices: index of the test in the chapters it appears; comma-separated list with the same length as chapters (e.g. "134, 12,10").

It would also be helpful to know the prerequisites for each test:
* whether they should be viewed with a paged media type
* whether they must be served over http
* whether they require user interaction
* whether they require a user CSS file

Can the "dinamic-pseudo-classes" be renamed to fix the spelling error?


Received on Monday, 27 September 2010 06:28:47 UTC