I wish I understood hg
authorRobin Berjon <robin@berjon.com>
Thu, 26 May 2011 18:17:11 +0200
changeset 19 ce0453cecb74
parent 18 997b3750dcd1 (current diff)
parent 15 84751fee3319 (diff)
child 20 89bcc8506c00
I wish I understood hg
--- a/contacts/tests/Overview.html	Thu May 26 18:14:35 2011 +0200
+++ b/contacts/tests/Overview.html	Thu May 26 18:17:11 2011 +0200
@@ -215,9 +215,7 @@
  <p>This document provides an overview of the test suite for the <a
    href="http://www.w3.org/TR/contacts-api/">Contacts API</a>  specification. The Working Group
 has developed this test suite so to have a test case for every conformance requirement in the specification. </p>
- <p><strong>Please note that this document puts a number <a href="requirements">requirements</a> on user agents, which must be supported in order to be able to run the tests. </strong></p>
- <p>The keywords <dfn title=""><em class="ct-samp">must</em></dfn>, <dfn title=""><em class="ct-samp">must not</em></dfn>, <dfn title=""><em class="ct-samp">should</em></dfn>, <dfn title=""><em class="ct-samp">recommended</em></dfn>, <dfn title=""><em class="ct-samp">may</em></dfn> and <dfn title=""><em class=
-  "ct-samp">optional</em></dfn> in this document are to be interpreted as described in <span>[RFC2119]</span>.</p>
  <h2>Status of this Test Suite</h2>
  <p>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.</p>
 <h2>Licenses and Contributions</h2>
@@ -232,41 +230,18 @@
 <h2 id="user-agent-requirements">Method used for testing </h2>
 <p>This specification adheres to the guidelines described in  <cite><a href="http://www.w3.org/TR/test-methodology/">A Method for Writing Testable Conformance Requirements</a></cite>. Please refer to that document for terminology and the approach that was taken to create this test suite. </p>
-<h2 id="requirements">User Agent Requirements
- <p>In addition to the specifications required to be supported by user
-   agents by the P&amp;C specification, some tests require, at a minimum,
- <ul>
-   <li><span>[HTML4.01]</span>
-     <ul>
-       <li>Although the HTML-based tests templates are written to conform to
-         the <a href="#html5">[HTML]</a> specification, the templates are
-         compatible with <span>[HTML4.01]</span>.</li>
-     </ul>
-   </li>
-   <li><span>[CSS1]</span>
-     <ul>
-       <li>The <code>background-color</code> property and the colors: <code>red</code>, <code>green</code>, and <code>#666</code>.</li>
-     </ul>
-   </li>
- </ul>
- <p>Without support for the above specifications, it may not be possible for a user agent to effectively run the test cases of the test suite (and false results may occur). 
+<p>The JavaScript-based tests rely on the <a href="http://w3c-test.org/resources/testharness.js">common JavaScript Test Harness</a> used by other Working Groups.</p>
 <h2 id="how-to-write-a-test">Automated testing</h2>
 <p>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's CVS repository.</p>
+  available through the W3C Mercurial repository.</p>
 <h2>How to get the tests and test descriptions</h2>
 <p><strong>Before you run the tests, please make sure you read this document thoroughly.</strong></p>
-<p>Tests can be downloaded using CVS using the following commands:</p>
-<pre>CVSROOT=:pserver:[email protected]:/sources/public cvs login 
+<p>Tests can be downloaded using Mercurial using the following commands:</p>
+<kbd>hg clone https://dvcs.w3.org/hg/dap</kbd>
-<p>Then enter the password <kbd>anonymous</kbd> when prompted, and then: </p>
-CVSROOT=:pserver:[email protected]:/sources/public cvs checkout 2009/dap/contacts/tests/
 <p>The Working Group also
   provides an <a href="test-suite.xml">XML file</a> that describes each test case, links to each test
   case, and identifies the assertion being tested.</p>
@@ -278,6 +253,7 @@
 <script src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
+<script>var SPEC_URL = "http://dev.w3.org/2009/dap/contacts/";</script>
 <script src="http://dev.w3.org/2006/waf/widgets-shared/javascript/ShowTestSuite.js"></script>
--- a/contacts/tests/test-suite.xml	Thu May 26 18:14:35 2011 +0200
+++ b/contacts/tests/test-suite.xml	Thu May 26 18:17:11 2011 +0200
@@ -5,17 +5,21 @@
 Tests that the UA implements navigator.contacts.findContacts
 <test id="ab" for="ta-ab" src="test-cases/find_empty_fields.html">
-Tests that the UA returns empty contacts when request sent with empty list of fields
+Tests that the UA triggers error callback when request sent with empty list of fields
 <test id="ac" for="ta-ac" src="test-cases/find_one_result.html">
 Tests that the UA returns expected results for pre-defined contact
+<test id="ak" for="ta-ak" src="test-cases/find_one_result.html">
+Tests that the UA returns only expected properties
 <test id="ad" for="ta-ad" src="test-cases/find_with_composed_field.html">
 Tests that the UA deals correctly with composed fields
 <test id="ae" for="ta-ae" src="test-cases/find_two_results.html">
-Tests that the UA returns expected results for pre-defined contact
+Tests that the UA returns expected multiple results for pre-defined contact
 <test id="af" for="ta-af" src="test-cases/find_with_array_composed_field.html">
 Tests that the UA deals correctly with array of composed fields
@@ -23,6 +27,9 @@
 <test id="ag" for="ta-ag" src="test-cases/single_task_queue.html">
 Tests that the UA returns pending operation error when firing two find in a row.
+<test id="ah" for="ta-ac" src="test-cases/find_all_fields.html">
+Tests that the UA returns correctly all fields