Test Suite for the Contacts API
- Maintainers:
- Dominique Hazael-Massieux, W3C
Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
Copyright © 2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document provides an overview of the test suite for the Contacts API specification. The Working Group has developed this test suite so to have a test case for every conformance requirement in the specification.
Publication of this test suite does not imply endorsement by the W3C Membership. This test suite is constantly evolving and the tests within in may be updated, replaced or obsoleted by other test at any time. When new tests become available, old obsoleted tests should be discarded. It is inappropriate to cite this document as other than a work in progress.
This test suite is distributed under the W3C test suite licensing scheme. Note that claims of performance can only be made against unaltered tests.
The Working Group encourages the public and W3C members to contribute tests. To contribute to a W3C Test Suite, see the policies and contribution forms.
This specification adheres to the guidelines described in A Method for Writing Testable Conformance Requirements. Please refer to that document for terminology and the approach that was taken to create this test suite.
The JavaScript-based tests rely on the common JavaScript Test Harness used by other Working Groups.
The Working Group does not provide an automated testing solution for this specification. However, every test case in the test suite is available through the W3C Mercurial repository.
Before you run the tests, please make sure you read this document thoroughly.
Tests can be downloaded using Mercurial using the following commands:
hg clone https://dvcs.w3.org/hg/dapThe Working Group also provides an XML file that describes each test case, links to each test case, and identifies the assertion being tested.
Vendors doing testing are strongly encouraged to submit their results to the working group. Having evidence that all tests in the test suite can be passed allows the specification to proceed along the W3C's Recommendation track.