public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 1/2] [gdb/testsuite] Add test-case gdb.tui/single-key.exp
Date: Tue,  6 Jun 2023 17:03:32 +0200	[thread overview]
Message-ID: <20230606150333.5206-1-tdevries@suse.de> (raw)

I noticed that there's no test-case excercising SingleKey mode, so add a test-case.

Tested on x86_64-linux.
---
 gdb/testsuite/gdb.tui/single-key.exp | 60 ++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)
 create mode 100644 gdb/testsuite/gdb.tui/single-key.exp

diff --git a/gdb/testsuite/gdb.tui/single-key.exp b/gdb/testsuite/gdb.tui/single-key.exp
new file mode 100644
index 00000000000..07c9b00cce5
--- /dev/null
+++ b/gdb/testsuite/gdb.tui/single-key.exp
@@ -0,0 +1,60 @@
+# Copyright 2023 Free Software Foundation, Inc.
+
+# 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/>.
+
+tuiterm_env
+
+Term::clean_restart 24 80
+if {![Term::enter_tui]} {
+    unsupported "TUI not supported"
+    return
+}
+
+set status_win { 0 15 80 1 }
+set command_win { 0 16 80 8 }
+
+# Check that the status window doesn't show Singlekey.
+set re "No process In:"
+Term::check_region_contents  "status window: initial" {*}$status_win $re
+
+# Enter single-key mode.  Check that the status window does show Singlekey.
+send_gdb "\030s"
+set re "No process \\(SingleKey\\) In:"
+gdb_assert { [Term::wait_for_region_contents {*}$status_win $re] } \
+    "status window: single-key mode"
+
+# Send "down command".
+send_gdb "d"
+gdb_assert { [Term::wait_for_region_contents {*}$command_win "No stack\\."] } \
+    "down using single-key d"
+
+# Quit single-key mode.
+send_gdb "q"
+gdb_assert { [Term::wait_for ""] } "quit using single-key q"
+
+# Enter single-key mode, again.
+send_gdb "\030s"
+
+# Send string that doesn't start with a single-key.
+send_gdb "abc"
+set re "$gdb_prompt abc"
+gdb_assert { [Term::wait_for_region_contents {*}$command_win $re] } \
+    "temporary command prompt"
+
+# Enter undefined command abc, and back to single-key mode.
+send_gdb "\n"
+
+# Exit single-key mode, now using C-x s.
+send_gdb "\030s"
+gdb_assert { [Term::wait_for ""] } "quit using C-x s"

base-commit: d3f340763bab7c74838ebb481fd7ff93acd9f00c
-- 
2.35.3


             reply	other threads:[~2023-06-06 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 15:03 Tom de Vries [this message]
2023-06-06 15:03 ` [PATCH 2/2] [gdb/tui] Delete line buffer when switching to singlekey Tom de Vries
2023-06-09 14:16   ` Tom Tromey
2023-06-09 14:37     ` Tom de Vries
2023-06-09 13:52 ` [PATCH 1/2] [gdb/testsuite] Add test-case gdb.tui/single-key.exp 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=20230606150333.5206-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).