Contributing to the CSS2.1 Test Suite

The CSS2.1 Test Suite still needs a lot of work, and the CSS Working Group can't finish it all by itself. Anyone can contribute: here are the guidelines.

• All tests must conform to the CSS2.1 Test Suite Guidelines.
• All tests must also adhere to the format guidelines.
• The tests are intended to be released under both the W3C Document License and the BSD 3-clause license, so you must give your explicit permission for us to use your contributions under these licenses.

The test suite is licensed under both the W3C Test Suite License and the 3-clause BSD License.

To give us permission to distribute your contribution under these two licenses, you need to fill out W3C's license grant form (unless you or your company is a member of the CSS Working Group, in which case you're covered already).

You can submit a new test by

1. Sending us permission to use the test as described above.
2. Sending the test to public-css-testsuite@w3.org either as a link or an attachment.

Please make sure submissions follow the CSS2.1 Test Suite Guidelines. New tests are subject to the review process. We may ask you to fix problems in your test and resubmit it before adding it to the test suite.

1. First check the Known Problems list to see if your problem has already been reported. If it hasn't, then
2. Send an email to public-css-testsuite@w3.org describing the problem
3. Ideally, also add it to the Known Problems list once your post shows up in the public-css-testsuite mail archives

To contribute a fix to an existing test, send an email to public-css-testsuite@w3.org with both

• an explanation of the problem or a reference to a previous message explaining the problem
• the precise changes necessary to fix the problem (preferably as a diff either against the CVS source copy or against the XHTML1.1 version)

Fixes to existing tests are also subject to the review process.

• You can subscribe to the public-css-testsuite mailing list and review test submissions as they come in.
• You can help fix test submissions in response to review comments.
• You can go through the issues marked VERIFYME in the Known Problems list, verify that they are indeed fixed in the latest version, and remove them from the known bugs list.

If you've waited at least a week and your contribution seems to be going nowhere, please complain to the test suite owner (currently fantasai). No, really, please do complain if this is the case; I'm probably just having some trouble staying on top of things and need a reminder or three.