Force tests to wait for brute force login event as they are fired in …

…a separate thread Closes keycloak#32942 Signed-off-by: Pedro Igor <[email protected]>
pedroigor · Oct 1, 2024 · 87db1d1 · 87db1d1
1 parent 3887ee3
commit 87db1d1
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/...an/tests/base/src/test/java/org/keycloak/testsuite/broker/AbstractAdvancedBrokerTest.java b/...an/tests/base/src/test/java/org/keycloak/testsuite/broker/AbstractAdvancedBrokerTest.java
@@ -29,6 +29,7 @@
 import org.keycloak.testsuite.util.OAuthClient;
 import org.keycloak.testsuite.util.RealmBuilder;
 import org.keycloak.testsuite.util.TestAppHelper;
+import org.keycloak.testsuite.util.WaitUtils;
 import org.openqa.selenium.TimeoutException;
 
 import jakarta.ws.rs.client.Client;
@@ -566,12 +567,12 @@ public void testPostBrokerLoginFlowWithOTP_bruteForceEnabled() {
 
             loginTotpPage.assertCurrent();
 
+            events.clear();
+
             // Login for 2 times with incorrect TOTP. This should temporarily disable the user
             loginTotpPage.login("bad-totp");
             Assert.assertEquals("Invalid authenticator code.", loginTotpPage.getInputError());
-
-            events.clear();
-
+            WaitUtils.waitForPageToLoad();
             loginTotpPage.login("bad-totp");
             Assert.assertEquals("Invalid authenticator code.", loginTotpPage.getInputError());