From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/8] Testing for the TUI
Date: Sun, 21 Jul 2019 18:49:00 -0000 [thread overview]
Message-ID: <20190721184910.26679-1-tom@tromey.com> (raw)
While working on another long set of TUI patches, I started
introducing bugs as I made less cosmetic changes.
So, I added a way to test the TUI. I was keeping this in my
development series, but I realized it would be better to land it
sooner, and then update the tests in the new series.
This series adds a terminal emulator to the gdb test suite, then
provides a few tests to exercise the TUI. The emulator isn't perfect
by any means -- occasionally I've had to implement a new CSI function
while writing a test -- but it's good enough so far.
If you examine the tests here, you'll see a few uses of setup_xfail.
These were all introduced when backporting to trunk, and will be
removed by my next TUI series.
There are plenty of tests that could still be written. Coverage in
the TUI is still just 63%.
Tom
next reply other threads:[~2019-07-21 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 18:49 Tom Tromey [this message]
2019-07-21 18:49 ` [PATCH 6/8] Add TUI resizing test Tom Tromey
2019-07-21 18:49 ` [PATCH 3/8] Add "layout split" test Tom Tromey
2019-07-21 18:49 ` [PATCH 5/8] Add TUI test for "list" Tom Tromey
2019-07-21 18:49 ` [PATCH 2/8] Add test for "layout asm" Tom Tromey
2019-07-26 11:11 ` Andrew Burgess
2019-07-26 18:50 ` Tom Tromey
2019-07-21 18:49 ` [PATCH 1/8] A virtual terminal for the test suite Tom Tromey
2019-07-21 18:49 ` [PATCH 7/8] Add test case for empty TUI windows Tom Tromey
2019-07-21 18:49 ` [PATCH 8/8] Add test that "file" shows "main" Tom Tromey
2019-07-21 18:49 ` [PATCH 4/8] Add TUI register window test 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=20190721184910.26679-1-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).