From 2fbafd16dcb40f047d9557fea15c4aa9d6e024ad Mon Sep 17 00:00:00 2001
From: Adam Williamson <awilliam@redhat.com>
Date: Tue, 2 Jul 2024 14:44:47 -0700
Subject: [PATCH] Tweak clocks timer test flow a little

It doesn't make sense to wait for a still screen while a timer is
running.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
---
 tests/applications/clocks/timer.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/applications/clocks/timer.pm b/tests/applications/clocks/timer.pm
index 921e2a26..867441f9 100644
--- a/tests/applications/clocks/timer.pm
+++ b/tests/applications/clocks/timer.pm
@@ -14,10 +14,10 @@ sub run {
     # Add a new alarm using the one minute button
     assert_screen("clocks_timer_page");
     assert_and_click("clocks_button_timer_minute");
-    wait_still_screen(2);
     # since GNOME 46, that was a 'quickstart', on older GNOME we
     # have to hit start; remove this when no more F39 testing
     if (check_screen("clocks_button_timer_start", 5)) {
+        wait_still_screen(2);
         click_lastmatch;
     }
     sleep(10);