CSS tests have some additional requirements for metadata.
Specification Links
<link rel="help" href="RELEVANT_SPEC_SECTION" />
The specification link elements provide a way to align the test with information in the specification being tested.
Example 1:
<link rel="help" href="http://www.w3.org/TR/CSS21/text.html#alignment-prop" />
Example 2:
<link rel="help" href="http://www.w3.org/TR/CSS21/text.html#alignment-prop" /> <link rel="help" href="http://www.w3.org/TR/CSS21/visudet.html#q7" /> <link rel="help" href="http://www.w3.org/TR/CSS21/visudet.html#line-height" /> <link rel="help" href="http://www.w3.org/TR/CSS21/colors.html#background-properties" />
Example 1 (one token applies):
<meta name="flags" content="invalid" />
Example 2 (multiple tokens apply):
<meta name="flags" content="ahem image scroll" />
Example 3 (no tokens apply):
<meta name="flags" content="" />
<meta name="assert" content="TEST ASSERTION" />
This element should contain a complete detailed statement expressing what specifically the test is attempting to prove. If the assertion is only valid in certain cases, those conditions should be described in the statement.
The assertion should not be:
The test assertion is optional. It helps the reviewer understand the goal of the test so that he or she can make sure it is being tested correctly. Also, in case a problem is found with the test later, the testing method (e.g. using color
to determine pass/fail) can be changed (e.g. to using background-color
) while preserving the intent of the test (e.g. testing support for ID selectors).
Examples of good test assertions: