From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Testing the installer Date: Sun, 12 Jan 2020 23:13:54 +0100 Message-ID: <87o8v8qq59.fsf@inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45944) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iqlUb-0003g1-AK for guix-devel@gnu.org; Sun, 12 Jan 2020 17:13:58 -0500 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: guix-devel 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 =E2=80=98run-form= =E2=80=99 calls would be replaced by =E2=80=98draw-form=E2=80=99 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=E2=80=99.