|
4 | 4 | <article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> |
5 | 5 | <info> |
6 | 6 | <title>XQSuite - Annotation-based Test Framework for XQuery</title> |
7 | | - <date>1Q18</date> |
| 7 | + <date>4Q18</date> |
8 | 8 | <keywordset> |
9 | 9 | <keyword>application-development</keyword> |
10 | 10 | <keyword>xquery</keyword> |
|
163 | 163 | external resource.</para> |
164 | 164 | </listitem> |
165 | 165 | </varlistentry> |
| 166 | + <varlistentry> |
| 167 | + <term><code>%test:name</code></term> |
| 168 | + <listitem> |
| 169 | + <para>Povide a more descriptive name for your test than the XQuery function name, which is the default.</para> |
| 170 | + </listitem> |
| 171 | + </varlistentry> |
166 | 172 | <varlistentry> |
167 | 173 | <term><code>%test:pending</code></term> |
168 | 174 | <listitem> |
|
295 | 301 | supported by many systems, for instance Jenkins. </para> |
296 | 302 | <para>For every XQuery module tested, <code>test:suite</code> creates a single <tag>testsuite</tag> |
297 | 303 | element. The result of each test run is output as a <tag>testcase</tag> element. It will be |
298 | | - empty if the test passed. If the test failed (meaning that the test did not meet its assertions, |
| 304 | + empty if the test passed. If the test failed (meaning that the test did not meet its assertions, |
299 | 305 | or that it raised an <literal>fn:error</literal>), there will be a <tag>failure</tag> element |
300 | 306 | containing the expected result of the function, and an <tag>output</tag> element with the |
301 | | - actual result. In the case that the test resulted in an unexpected error that is not covered by |
302 | | - <literal>fn:error</literal>, there will be an <tag>error</tag> element with the error type and |
303 | | - message. The <tag>testsuite</tag> element will also contain the timestamp when the tests began, |
304 | | - the duration of the tests, and a count of the number of tests, failed tests, pending tests, and |
305 | | - tests that raised unexpected errors not covered by <literal>fn:error</literal>. Here is a sample |
| 307 | + actual result. In the case that the test resulted in an unexpected error that is not covered by |
| 308 | + <literal>fn:error</literal>, there will be an <tag>error</tag> element with the error type and |
| 309 | + message. The <tag>testsuite</tag> element will also contain the timestamp when the tests began, |
| 310 | + the duration of the tests, and a count of the number of tests, failed tests, pending tests, and |
| 311 | + tests that raised unexpected errors not covered by <literal>fn:error</literal>. Here is a sample |
306 | 312 | showing a failed test:</para> |
307 | 313 | <programlisting language="xml" xlink:href="listings/listing-8.xml"/> |
308 | 314 | </sect1> |
|
0 commit comments