From 2fc6991ad0d91fea1d2ab4ab50c4691830f60389 Mon Sep 17 00:00:00 2001 From: Henri Sara Date: Mon, 2 May 2016 10:16:55 +0300 Subject: Fix CriticalNotificationsTest on Chrome Without this fix, a mismatch in screenshots causes a non-screenshot test failure. Change-Id: I6fb157a764ef1ec594836cbeceacd898820e7e11 --- .../com/vaadin/tests/application/CriticalNotificationsTest.java | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'uitest') diff --git a/uitest/src/test/java/com/vaadin/tests/application/CriticalNotificationsTest.java b/uitest/src/test/java/com/vaadin/tests/application/CriticalNotificationsTest.java index 6229edc1ee..51fe3dfd06 100644 --- a/uitest/src/test/java/com/vaadin/tests/application/CriticalNotificationsTest.java +++ b/uitest/src/test/java/com/vaadin/tests/application/CriticalNotificationsTest.java @@ -72,6 +72,12 @@ public class CriticalNotificationsTest extends MultiBrowserThemeTest { click($(CheckBoxElement.class).caption("Include details").first()); } $(ButtonElement.class).caption(buttonCaption).first().click(); + + // some critical notifications invalidate the session, and if a + // screenshot does not match, waitForVaadin would cause the screenshot + // comparison to crash because of a missing session + testBench().disableWaitForVaadin(); + // Give the notification some time to animate sleep(1000); compareScreen($(NotificationElement.class).first(), -- cgit v1.2.3