Making EnteringInteractiveModeShouldWait more reliable

Lombiq · Jan 12, 2025 · 7e2ce01 · 7e2ce01
1 parent 2db3a83
commit 7e2ce01
Showing 1 changed file with 7 additions and 3 deletions.
diff --git a/Lombiq.Tests.UI.Samples/Tests/InteractiveModeTests.cs b/Lombiq.Tests.UI.Samples/Tests/InteractiveModeTests.cs
@@ -1,6 +1,8 @@
 using Lombiq.Tests.UI.Extensions;
+using Lombiq.Tests.UI.Helpers;
 using OpenQA.Selenium;
 using Shouldly;
+using System;
 using System.Diagnostics.CodeAnalysis;
 using System.Threading.Tasks;
 using Xunit;
@@ -57,9 +59,11 @@ await Task.WhenAll(
                     Task.Run(
                         async () =>
                         {
-                            // Ensure that the interactive mode polls for status at least once, so the arbitrary waiting
-                            // actually works in a real testing scenario.
-                            await Task.Delay(5000, context.Configuration.TestCancellationToken);
+                            ReliabilityHelper.DoWithRetriesOrFail(
+                                () => context.Driver.WindowHandles.Count > 1,
+                                TimeSpan.FromSeconds(5));
+
+                            context.SwitchToLastWindow();
 
                             await context.ClickReliablyOnAsync(By.ClassName("interactive__continue"));
                         },