From e2f47e127c9f57031732ec863629ae016957df4b Mon Sep 17 00:00:00 2001 From: Henri Sara Date: Thu, 31 Aug 2017 09:08:10 +0300 Subject: [PATCH] Make BaseThemeTest more stable on IE11 Try to make the test more stable by using a different way of detecting the presence of a notification. This approach is used e.g. in GridComponentsTest. --- .../java/com/vaadin/tests/components/uitest/ThemeTest.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/uitest/src/test/java/com/vaadin/tests/components/uitest/ThemeTest.java b/uitest/src/test/java/com/vaadin/tests/components/uitest/ThemeTest.java index f6f88baafe..39ee947fb6 100644 --- a/uitest/src/test/java/com/vaadin/tests/components/uitest/ThemeTest.java +++ b/uitest/src/test/java/com/vaadin/tests/components/uitest/ThemeTest.java @@ -129,7 +129,8 @@ public abstract class ThemeTest extends MultiBrowserTest { private void testNotification(int id, String identifier) throws IOException { $(ButtonElement.class).id("notifButt" + id).click(); - waitForElementPresent(By.className("v-Notification")); + // For some reason, this seems to be more reliable on IE11 + waitUntil(driver -> isElementPresent(NotificationElement.class), 10); compareScreen(identifier); $(NotificationElement.class).first().close(); } -- 2.39.5