-
Notifications
You must be signed in to change notification settings - Fork 43
/
Copy pathtestspec.html
45 lines (45 loc) · 1.02 KB
/
testspec.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
<html>
<head>
<title>Test Specifications</title>
</head>
<body>
<h1>Test Specifications</h1>
<p>For each normative assertion, state how it is to be tested.
This should include the tools used, and links to any test cases.
An assertion may require more than one test for particular configurations or
combinations of options.
Ideally, for each test, if possible a counterexample that fails the
test should also be provided.
</p>
<dl>
<!-- EXAMPLE
<dt>unique-id:</dt>
<dd>
<span class="testspec" id="unique-id">
<strong>Test Method:</strong> one of
Unknown
Parent
JSON Schema
WoT-Test Bench,
Manual via (a specific Tool, eg Postman, curl, etc)
<ul>
<li>
If no test available:
NO TEST EXISTS;
(how to resolve, for example)
NEEDS SCHEMA IN AssertionTester
NEEDS SPECIALIZED SCRIPT
</li>
<li>
Example = URL of the TD
</li>
<li>
Additional information: E.g. ASSERTION NOT CLEAR
</li>
</ul>
</span>
</dd>
-->
</dl>
</body>
</html>