aboutsummaryrefslogtreecommitdiff
path: root/doc/testscript.cli
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2019-06-05 16:14:52 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2019-06-05 16:14:52 +0300
commit952c3b41399247615fe3a3c6e5109199aacf73b5 (patch)
tree1b6bd246df528efd0ff4c04e3f8638597c569e69 /doc/testscript.cli
parent2ea2446b8ff5c08469d16a0deb951b0962924cec (diff)
Add test id verification
Diffstat (limited to 'doc/testscript.cli')
-rw-r--r--doc/testscript.cli7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/testscript.cli b/doc/testscript.cli
index 41f8111..4433375 100644
--- a/doc/testscript.cli
+++ b/doc/testscript.cli
@@ -273,9 +273,10 @@ The description lines precede the test command. They start with a colon
The recommended format for \c{<id>} is \c{<keyword>-<keyword>...} with at
least two keywords. The id is used in diagnostics, to name the test working
directory, as well as to run individual tests. It can only contain
-alphanumeric characters as well as underscores and minuses. The recommended
-style for \c{<summary>} is that of the \c{git(1)} commit summary. The detailed
-description is free-form. Here are some examples (\c{#} starts a comment):
+alphanumeric characters as well as underscores, pluses, and minuses. The
+recommended style for \c{<summary>} is that of the \c{git(1)} commit summary.
+The detailed description is free-form. Here are some examples (\c{#} starts a
+comment):
\
# Only id.