Update test manifest and documentation with remote-doc tests.
authorGregg Kellogg <gregg@kellogg-assoc.com>
Tue, 03 Sep 2013 16:57:57 -0700
changeset 1966 496469602088
parent 1965 203b669abb9a
child 1967 95026aded01e
Update test manifest and documentation with remote-doc tests.
test-suite/index.html
test-suite/manifest.jsonld
--- a/test-suite/index.html	Tue Sep 03 16:43:58 2013 -0700
+++ b/test-suite/index.html	Tue Sep 03 16:57:57 2013 -0700
@@ -144,12 +144,21 @@
           <li><em>normalize</em> tests have <em>input</em> and <em>expected</em> documents, and
             may have <em>options</em>. The <em>expected</em> results
             can be compared using string comparison with the processor output.</li>
+          <li><em>fromRdf</em> tests have <em>input</em> and <em>expected</em> documents, and
+            may have <em>options</em>. The <em>expected</em> results
+            can be compared using JSON object comparison with the processor output.</li>
+          <li><em>remote-doc</em> tests have <em>input</em> and <em>expected</em> documents, and
+            may have <em>options</em>. These tests are setup somewhat differently, as they
+            depend on specific HTTP header results to invoke document loading behavior.
+            The <em>expected</em> results are either an expected error or result document,
+            depending on if the test type include <code>NegativeEvaluationTest</code> or <code>PositiveEvaluationTest</code>.
+            For negative tests, the <em>expected</em> result
+            is an exception matching an error code defined for <em>JsonLdErrorCode</em>.
+            For positive tests, the <em>expected</em> results
+            can be compared using JSON object comparison with the processor output.</li>
           <li><em>toRdf</em> tests have <em>input</em> and <em>expected</em> documents, and
             may have <em>options</em>. The <em>expected</em> results
             can be compared using string comparison with the processor output.</li>
-          <li><em>fromRdf</em> tests have <em>input</em> and <em>expected</em> documents, and
-            may have <em>options</em>. The <em>expected</em> results
-            can be compared using JSON object comparison with the processor output.</li>
           </ul>
           <p>To run the tests, create a test runner which will run through each test manifest
             and execute the tests defined within the manifest using the rules associated with
--- a/test-suite/manifest.jsonld	Tue Sep 03 16:43:58 2013 -0700
+++ b/test-suite/manifest.jsonld	Tue Sep 03 16:57:57 2013 -0700
@@ -12,6 +12,7 @@
     "tests/frame-manifest.jsonld",
     "tests/fromRdf-manifest.jsonld",
     "tests/normalize-manifest.jsonld",
+    "tests/remote-doc-manifest.jsonld",
     "tests/toRdf-manifest.jsonld"
   ]
 }