Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH v2 5/8] Add TUI test for "list"
Date: Fri, 26 Jul 2019 18:51:00 -0000	[thread overview]
Message-ID: <20190726185134.1856-6-tom@tromey.com> (raw)
In-Reply-To: <20190726185134.1856-1-tom@tromey.com>

This adds a test to check that the "list" command will update the TUI
source window.

2019-07-21  Tom Tromey  <tom@tromey.com>

	* gdb.tui/list.exp: New file.
---
 gdb/testsuite/ChangeLog        |  4 ++++
 gdb/testsuite/gdb.tui/list.exp | 40 ++++++++++++++++++++++++++++++++++
 2 files changed, 44 insertions(+)
 create mode 100644 gdb/testsuite/gdb.tui/list.exp

diff --git a/gdb/testsuite/gdb.tui/list.exp b/gdb/testsuite/gdb.tui/list.exp
new file mode 100644
index 00000000000..0229b81c8a7
--- /dev/null
+++ b/gdb/testsuite/gdb.tui/list.exp
@@ -0,0 +1,40 @@
+# Copyright 2019 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/>.
+
+# Ensure that "list" will switch to the source view.
+
+load_lib "tuiterm.exp"
+
+standard_testfile tui-layout.c
+
+if {[build_executable "failed to prepare" ${testfile} ${srcfile}] == -1} {
+    return -1
+}
+
+Term::clean_restart 24 80 $testfile
+if {![Term::enter_tui]} {
+    unsupported "TUI not supported"
+}
+
+set text [Term::get_all_lines]
+gdb_assert {[regexp "No Source Available" $text]} "initial source listing"
+
+Term::command "layout asm"
+set text [Term::get_all_lines]
+gdb_assert {[regexp "$hex <main>" $text]} "asm window shows main"
+
+Term::command "list main"
+set text [Term::get_all_lines]
+gdb_assert {[regexp "21 *return 0" $text]} "list main"
-- 
2.17.2


  parent reply	other threads:[~2019-07-26 18:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 18:51 [PATCH v2 0/8] TUI testing Tom Tromey
2019-07-26 18:51 ` [PATCH v2 2/8] Add test for "layout asm" Tom Tromey
2019-07-26 18:51 ` [PATCH v2 3/8] Add "layout split" test Tom Tromey
2019-07-26 18:51 ` [PATCH v2 6/8] Add TUI resizing test Tom Tromey
2019-07-26 18:51 ` [PATCH v2 4/8] Add TUI register window test Tom Tromey
2019-07-26 18:51 ` [PATCH v2 1/8] A virtual terminal for the test suite Tom Tromey
2019-07-27 16:01   ` Andrew Burgess
2019-07-28  2:56     ` Tom Tromey
2019-07-31 15:44   ` minimal tcl version for gdb " Tom de Vries
2019-07-31 17:46     ` Tom Tromey
2019-08-01  9:39       ` Tom de Vries
2019-08-01 15:48         ` Tom Tromey
2019-07-26 18:51 ` Tom Tromey [this message]
2019-07-26 18:51 ` [PATCH v2 7/8] Add test case for empty TUI windows Tom Tromey
2019-07-26 18:51 ` [PATCH v2 8/8] Add test that "file" shows "main" 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=20190726185134.1856-6-tom@tromey.com \
    --to=tom@tromey.com \
    --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