From: Henri Sara <hesara@vaadin.com>
Date: Fri, 6 May 2016 10:02:06 +0000 (+0300)
Subject: Fix CriticalNotificationsTest on Chrome
X-Git-Tag: 7.6.6~6
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=fdcd026a744b7217129861a918f7bd53deafbb80;p=vaadin-framework.git

Fix CriticalNotificationsTest on Chrome

Without this fix, a mismatch in screenshots causes a non-screenshot
test failure.

Change-Id: Ib211f6f436d9d414642bf40f6a1b55dcf03c7b85
---

diff --git a/uitest/src/com/vaadin/tests/application/CriticalNotificationsTest.java b/uitest/src/com/vaadin/tests/application/CriticalNotificationsTest.java
index 6229edc1ee..51fe3dfd06 100644
--- a/uitest/src/com/vaadin/tests/application/CriticalNotificationsTest.java
+++ b/uitest/src/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(),