From 02b9e2eb667f1ec385a73b04196eb1cf5bb699d4 Mon Sep 17 00:00:00 2001 From: Timur Sufiev <tsufiev@mirantis.com> Date: Thu, 25 Aug 2016 13:44:59 +0300 Subject: [PATCH] Fix intermittent integration test failures related to messages Some recent changes in python selenium bindings library made it do certain things faster. That rendered our code for accessing Horizon messages too restrictive, since it didn't wait a second. Previously, when selenium queries took longer, the modal message had enough time to appear, but now sometimes selenium is able to query the browser during a narrow window when the spinner from a previous modal have already disappeared, but the modal message still hasn't been rendered. Adapt to these change by introducing a small (0.1 seconds) margin to wait until message element appears. Change-Id: I8f23ecaac9d007a1d3302eb9425d4064f438ca14 --- openstack_dashboard/test/integration_tests/regions/messages.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openstack_dashboard/test/integration_tests/regions/messages.py b/openstack_dashboard/test/integration_tests/regions/messages.py index 866be250cb..2d46a1fdf4 100644 --- a/openstack_dashboard/test/integration_tests/regions/messages.py +++ b/openstack_dashboard/test/integration_tests/regions/messages.py @@ -30,7 +30,7 @@ class MessageRegion(baseregion.BaseRegion): self._default_src_locator = self._msg_locator(level) # NOTE(tsufiev): we cannot use self._turn_off_implicit_wait() at this # point, because the instance is not initialized by ancestor's __init__ - driver.implicitly_wait(0) + driver.implicitly_wait(0.1) try: super(MessageRegion, self).__init__(driver, conf) except NoSuchElementException: