From a02d30f90c2879106faded8df9133087332de676 Mon Sep 17 00:00:00 2001 From: Abdessamad Derraz <3028866+Abdess@users.noreply.github.com> Date: Mon, 9 Nov 2026 20:06:44 +0100 Subject: [PATCH] fix: wait for the Confirm count in the tap test Confirm has no Install row until its dry run ends, so an Enter sent on its title alone fell on "Counting the files" and did nothing on the runner. The test now waits for "Counted again for these choices", drawn once the Install row exists. --- tests/test_install_tui.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tests/test_install_tui.py b/tests/test_install_tui.py index e14c35e8f..ec324b6d7 100644 --- a/tests/test_install_tui.py +++ b/tests/test_install_tui.py @@ -12374,10 +12374,10 @@ class TapsOnAPtySeeFirst(unittest.TestCase): break term.send("\x1b[A") term.send("\r") - # The changed choices are counted again on Confirm. Waiting on the - # bare title matched the screen before it, and a runner that drew - # Confirm after one settle never pressed Enter there. - term.wait("RetroBIOS: Confirm") + # The changed choices are counted again on Confirm, which has no + # Install row until its dry run ends: Enter sent on the title alone + # fell on "Counting the files" and did nothing on a slow runner. + term.wait("Counted again for these choices") term.settle() term.send("\r") term.wait("files installed")