CSS tests have some particular requirements for metadata. ## Title element ``` html [Test Area]: [Title/Scope of Test] or [Test Area] Reference File ``` The title appears in the generated index, so make sure it is concise and descriptive. The role of the title is to identify what specific detail of a feature or combination of features is being tested, so that someone looking through an index can see quickly what's tested in which file. In most cases, this description should not require more than 5 or 6 words. There is no need to provide the chapter or section in the title. For reference file, the titles should not be specific to a test case as these files may be used by multiple different tests. Bad examples: ``` html CSS Test: Border Conflict Resolution CSS Regions auto-height Reference ``` Good examples: ``` html CSS Test: Border Conflict Resolution (width) - hidden/double CSS Reference File ``` For CSS specifications other than CSS 2.1, you can include the module name somewhere before the colon, like "CSS Selectors Test:" or "CSS Test (Selectors):". Do not include the module version number, since the test might get reused for the next version. ### Credits ``` html ``` Credits provide a way to identify the person or organization that created the test and/or holds copyright in the test. This is useful for reviewing purposes and for asking questions about the individual test. A test can have multiple author credits if necessary. Example 1: ``` html ``` Example 2: ``` html ``` Example 3: ``` html ``` ### Reviewer ``` html ``` If a test has passed review, then the reviewer should note this by adding his or her name as a reviewer, along with the date of the review. A test can have multiple reviewers if necessary. A reviewer must be a person, not an organization. Example 1: ``` html ``` Example 2: ``` html ``` If a test would pass review with some (non-metadata) changes and the reviewer chooses to make these changes, then the reviewer should add his or her name as a reviewer-author, along with the date of the review, when checking in those changes. This indicates that the reviewer-author approves of the original author's test when taken with these proposed changes, and that someone else (possibly the original author) must review the changes. The test is fully reviewed only when the latest reviewer did not also contribute changes to the test at the time of the review. Example of a fully-reviewed test: ``` html ``` This test was written by Bert Bos, then reviewed by Boris Zbarsky, who made some corrections before deeming it acceptable. Those corrections were then reviewed and accepted by Bert Bos. ### Specification Links Specification Links ``` html ``` The specification link elements provide a way to align the test with information in the specification being tested. * Links should link to relevant sections within the specification * Use the anchors from the specification's Table of Contents * A test can have multiple specification links * Always list the primary section that is being tested as the first item in the list of specification links * Order the list from the most used/specific to least used/specific * There is no need to list common incidental features like the color green if it is being used to validate the test unless the case is specifically testing the color green * If the test is part of multiple test suites, link to the relevant sections of each spec. Example 1: ``` html ``` Example 2: ``` html ``` ### Reference Links *Reftests only* ``` html ``` The reference link elements are used in reftests and provide the list of reference file(s) that the test should be compared to. * ```match``` references must be files that render identically to the test, but use an alternate means to do so * Multiple match references are used when the test can match any of the reference files * If a test requires multiple match references that all need to match (for example, to catch when a reference fails in the same way the test does), then chain the references together, i.e.: place reference links to the additional match references in the reference files. It is recommended that the chained reference files form a loop (e.g.: a → b → c → a) so that a test linking to any reference in the chain will find all the references. * ```mismatch``` references are files that render differently than the test file. A test may have any number of mismatch references. The test is considered to fail if it renders the same as any of the mismatch references. * Note that reference files may themselves have mismatch references. In that case the reference file must not render the same as any of its mismatch references in order to be considered valid. If a reference is considered invalid (by the fact of not matching any of its match references, or matching any of its mismatch references), then a test that refers to the reference will be considered to have failed. * Reference files may be dedicated reference files, images, or other tests Example 1: ``` html ``` Example 2: ``` html ``` ### Requirement Flags
Token Description
ahem Test requires Ahem font
animated Test is animated in final state. (Cannot be verified using reftests/screenshots.)
asis The test has particular markup formatting requirements and cannot be re-serialized.
combo Test, which must have an unsuffixed filename number, is strictly the union of all the suffixed tests with the same name and number. (See File name format, below.)
dom Requires support for JavaScript and the Document Object Model ( DOM)
font Requires a specific font to be installed. (Details must be provided and/or the font linked to in the test description)
history User agent session history is required. Testing :visited is a good example where this may be used.
HTMLonly Test case is only valid for HTML
http Requires HTTP headers
image Requires support for bitmap graphics and the graphic to load
interact Requires human interaction (such as for testing scrolling behavior)
invalid Tests handling of invalid CSS. Note: This case contains CSS properties and syntax that may not validate.
may Behavior tested is preferred but OPTIONAL. [RFC2119]
namespace Requires support for XML Namespaces
nonHTML Test case is only valid for formats besides HTML (e.g. XHTML or arbitrary XML)
paged Only valid for paged media
scroll Only valid for continuous (scrolling) media
should Behavior tested is RECOMMENDED, but not REQUIRED. [RFC2119]
speech Device supports audio output. Text-to-speech (TTS) engine installed
svg Requires support for vector graphics (SVG)
userstyle Requires a user style sheet to be set
32bit Assumes a 32-bit integer as the minimum (-2147483648) or maximum (2147483647) value
96dpi Assumes 96dpi display
Example 1 (one token applies): ``` html ``` Example 2 (multiple tokens apply): ``` html ``` Example 3 (no tokens apply): ``` html ``` ### Test Assertions ``` html ``` 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: * A copy of the title text * A copy of the test verification instructions * A duplicate of another assertion in the test suite * A line or reference from the CSS specification unless that line is a complete assertion when taken out of context. 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: * "This test checks that a background image with no intrinsic size covers the entire padding box." * "This test checks that 'word-spacing' affects each space (U+0020) and non-breaking space (U+00A0)." * "This test checks that if 'top' and 'bottom' offsets are specified on an absolutely-positioned replaced element, then any remaining space is split amongst the 'auto' vertical margins." * "This test checks that 'text-indent' affects only the first line of a block container if that line is also the first formatted line of an element."