From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: Testing the installer
Date: Sun, 12 Jan 2020 23:13:54 +0100 [thread overview]
Message-ID: <87o8v8qq59.fsf@inria.fr> (raw)
Hello Guix!
One of the lessons from the 1.0.0 screw-up was that we should test the
graphical installer itself:
https://guix.gnu.org/blog/2019/gnu-guix-1.0.1-released/
I think we should try to do that before the next release; not doing it
means testing by hand, which also takes a lot of time.
One idea that I had was that we could change the installer so that it
listens for connections on some pre-defined Unix-domain socket. When it
gets a connection, it would perform a dialog with its client: sent it a
summary of the current form, wait for its choice, and so on. The forms
would thus be unavailable from the keyboard: essentially ‘run-form’
calls would be replaced by ‘draw-form’ calls in that mode.
Our test infrastructure would thus connect (from a marionette) to the
installer and participate in that dialog. It could even take a QEMU
screenshot at each step.
How does that sound? Am I overlooking things?
I guess the difficulty will be to represent questions and answers.
Ludo’.
next reply other threads:[~2020-01-12 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 22:13 Ludovic Courtès [this message]
2020-01-12 23:34 ` Testing the installer sirgazil
2020-01-20 17:49 ` sirgazil
2020-01-14 8:02 ` Mathieu Othacehe
2020-01-22 22:27 ` Ludovic Courtès
2020-01-23 9:41 ` Mathieu Othacehe
2020-01-23 11:21 ` Gábor Boskovits
2020-01-23 23:07 ` Bengt Richter
2020-01-24 7:48 ` Gábor Boskovits
2020-01-24 9:23 ` Ludovic Courtès
2020-01-23 14:54 ` Ludovic Courtès
2020-01-20 11:47 ` Jonathan Brielmaier
-- strict thread matches above, loose matches on Subject: below --
2018-06-13 3:57 swedebugia
2018-06-13 19:47 ` Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8v8qq59.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.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.savannah.gnu.org/cgit/guix.git
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).