From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: gdb-patches@sourceware.org
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Subject: [RFAv2 2/2] Add a selftest that checks documentation invariants.
Date: Sat, 03 Aug 2019 13:39:00 -0000 [thread overview]
Message-ID: <20190803133921.20154-3-philippe.waroquiers@skynet.be> (raw)
In-Reply-To: <20190803133921.20154-1-philippe.waroquiers@skynet.be>
Several approaches were discussed (mail or irc) to verify the invariants of
the GDB help documentation : checking with apropos ., modifying add_cmd
to do the check and output a warning, implement maintenance check-doc.
A selftest was finally chosen as:
* this can be run on demand, including by users if they want
to check user defined commands.
* it does not interact with the normal behaviour of apropos, define,
python, ...
(such as output warnings when a user defines a command help that
does not respect the doc).
* when the selftest runs, it checks the user defined and python
defined commands currently defined.
gdb/ChangeLog
* unittests/help-doc-selftests.c: New file.
* Makefile.in: Add the new file.
---
gdb/Makefile.in | 1 +
gdb/unittests/help-doc-selftests.c | 106 +++++++++++++++++++++++++++++
2 files changed, 107 insertions(+)
create mode 100644 gdb/unittests/help-doc-selftests.c
diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index 01ff0c0c20..b689769e13 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -414,6 +414,7 @@ SUBDIR_UNITTESTS_SRCS = \
unittests/environ-selftests.c \
unittests/format_pieces-selftests.c \
unittests/function-view-selftests.c \
+ unittests/help-doc-selftests.c \
unittests/lookup_name_info-selftests.c \
unittests/memory-map-selftests.c \
unittests/memrange-selftests.c \
diff --git a/gdb/unittests/help-doc-selftests.c b/gdb/unittests/help-doc-selftests.c
new file mode 100644
index 0000000000..8335ad581e
--- /dev/null
+++ b/gdb/unittests/help-doc-selftests.c
@@ -0,0 +1,106 @@
+/* Self tests for help doc for GDB, the GNU debugger.
+
+ Copyright (C) 2019 Free Software Foundation, Inc.
+
+ This file is part of GDB.
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>. */
+
+#include "defs.h"
+#include "cli/cli-cmds.h"
+#include "cli/cli-decode.h"
+#include "gdbsupport/selftest.h"
+
+namespace selftests {
+namespace help_doc_tests {
+
+static unsigned int nr_failed_invariants;
+
+/* Report a broken invariant and increments nr_failed_invariants. */
+
+static void
+broken_doc_invariant (const char *prefix, const char *name, const char *msg)
+{
+ fprintf_filtered (gdb_stdout,
+ "help doc broken invariant: command '%s%s' help doc %s\n",
+ prefix, name, msg);
+ nr_failed_invariants++;
+}
+
+/* Recursively walk the commandlist structures, and check doc invariants:
+ - The first line of the doc must end with a '.'.
+ - the doc must not end with a new line.
+ If an invariant is not respected, produce a message and increment
+ nr_failed_invariants.
+ Note that we do not call SELF_CHECK in this function, as we want
+ all commands to be checked before making the test fail. */
+
+static void
+check_doc (struct cmd_list_element *commandlist, const char *prefix)
+{
+ struct cmd_list_element *c;
+
+ /* Walk through the commands. */
+ for (c=commandlist;c;c=c->next)
+ {
+ /* Checks the doc has a first line terminated with a '.'. */
+ const char *p = c->doc;
+
+ while (*p && *p != '\n')
+ p++;
+ if (p == c->doc)
+ broken_doc_invariant
+ (prefix, c->name,
+ "is missing the first line terminated with a '.' character");
+ else if (*(p-1) != '.')
+ broken_doc_invariant
+ (prefix, c->name,
+ "first line is not terminated with a '.' character");
+
+ /* Checks the doc is not terminated with a new line. */
+ if (c->doc[strlen (c->doc) - 1] == '\n')
+ broken_doc_invariant
+ (prefix, c->name,
+ "has a superfluous trailing end of line");
+
+ /* Check if this command has subcommands and is not an
+ abbreviation. We skip checking subcommands of abbreviations
+ in order to avoid duplicates in the output. */
+ if (c->prefixlist != NULL && !c->abbrev_flag)
+ {
+ /* Recursively call ourselves on the subcommand list,
+ passing the right prefix in. */
+ check_doc (*c->prefixlist, c->prefixname);
+ }
+ }
+}
+
+static void
+help_doc_invariants_tests ()
+{
+ nr_failed_invariants = 0;
+ check_doc (cmdlist, "");
+ SELF_CHECK (nr_failed_invariants == 0);
+}
+
+} /* namespace help_doc_tests */
+} /* namespace selftests */
+
+void
+_initialize_help_doc_selftests ()
+{
+ selftests::register_test
+ ("help_doc_invariants",
+ selftests::help_doc_tests::help_doc_invariants_tests);
+}
--
2.20.1
next prev parent reply other threads:[~2019-08-03 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 13:39 [RFAv2 0/2] Make first and last lines of 'command help documentation' consistent + add a test Philippe Waroquiers
2019-08-03 13:39 ` Philippe Waroquiers [this message]
2019-08-06 18:43 ` [RFAv2 2/2] Add a selftest that checks documentation invariants Tom Tromey
2019-08-06 22:21 ` Philippe Waroquiers
2019-08-07 2:06 ` Tom Tromey
2019-08-03 13:39 ` [RFAv2 1/2] Make first and last lines of 'command help documentation' consistent Philippe Waroquiers
2019-08-06 18:30 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190803133921.20154-3-philippe.waroquiers@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox