How to Create a Test
If you decide to create a test, please follow these minimum requirements: ConformanceTestsRequirements
Current Tests
This is not a test suite. A test suite is a package of identified test cases which have been acknowledged being buggy (accepted by the group) and that is versionned and stable. There's a need for a tarball when the test suite will be ready.
- BaseURIConformanceTests . . . . 1 match
- ConformanceTests . . . . 1 match
- LinkConformanceTests . . . . 1 match
- OrderConformanceTests . . . . 1 match
- TitleConformanceTests . . . . 1 match
- UpdatedConformanceTests . . . . 1 match
- XhtmlContentDivConformanceTests . . . . 1 match
- XmlBaseConformanceTests . . . . 1 match
- XmlNamespaceConformanceTests . . . . 1 match
Related tests
-
Aggregator client HTTP tests - status codes and common HTTP headers **
-
Atom autodiscovery test suite - clients are not required to support AutoDiscovery, but if they do, they MUST support the entire test suite
** Slight inconsistency here - clients MUST handle 420 correctly, but the behaviour is defined in terms of 400, which is only a SHOULD.
References
-
There doesn't appear to be any IETF or OASIS quality/testing references. ???
-
QA Specification Guidelines -- The goal of this document is to help W3C editors write better specifications, by making a specification easier to interpret without ambiguity and clearer as to what is required in order to conform.
-
QA Framework: Test Guidelines -- The principal goal of this document is to help W3C Working Groups to develop more useful and usable test materials. The material is presented as a set of organizing guidelines and verifiable checkpoints.
-
The Matrix of W3C specifications -- check out the test suites and implementation reports.