From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: A second test release before 5.9 final?
Date: Sun, 01 May 2022 18:49:20 +0100 [thread overview]
Message-ID: <f09c81e9025022262240643dfb4365b8022afded.camel@ntlworld.com> (raw)
In-Reply-To: <CAH+w=7bby1GiKxTL9Y3M6Xuhe56EQdRHDsabbShfWNLkdkxhsg@mail.gmail.com>
On Sun, 2022-05-01 at 09:50 -0700, Bart Schaefer wrote:
> I'm not sure how to write a test for 50134 because it requires
> starting an interactive shell, waiting several seconds, then sending
> it a SIGINT and discovering whether it exited immediately or N seconds
> later.
Really interactive tests (beyond the level of simulated keystrokes or
delays) is really hard to test robustly. Certainly what we've got at
the moment doesn't cut the mustard. I had a quick look a while ago for
something that might be more robust but didn't see anything that looked
like it would work out of the box, and I certainly don't think any of us
are going to be doing it from scratch.
pws
next prev parent reply other threads:[~2022-05-01 17:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 18:31 Bart Schaefer
2022-04-30 21:41 ` dana
2022-05-01 14:52 ` Daniel Shahaf
2022-05-01 16:50 ` Bart Schaefer
2022-05-01 17:38 ` Daniel Shahaf
2022-05-02 2:24 ` Jun T
2022-05-02 3:10 ` Bart Schaefer
2022-05-02 4:09 ` Jun T
2022-05-02 12:58 ` Daniel Shahaf
2022-05-01 17:49 ` Peter Stephenson [this message]
2022-05-01 18:09 ` [PATCH] Test for 50101 Bart Schaefer
2022-05-01 19:09 ` [PATCH] Tests for 50126, 50136, and 50149 Bart Schaefer
2022-05-02 4:59 ` Jun T
2022-05-02 5:15 ` Bart Schaefer
2022-05-02 5:46 ` Jun T
2022-05-02 13:14 ` Jun. T
2022-05-02 16:26 ` Bart Schaefer
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=f09c81e9025022262240643dfb4365b8022afded.camel@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).