summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/toaster/tests
diff options
context:
space:
mode:
authorElliot Smith <elliot.smith@intel.com>2016-04-26 17:12:52 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-06-15 08:35:04 +0100
commitef72321fe42206ded3d4cf32b5a31747483c6d85 (patch)
treee0495b811afd237b73c0140fc670b9663ccc2c01 /bitbake/lib/toaster/tests
parentdd764003ea2cb9449f838146183f17873a902e48 (diff)
downloadpoky-ef72321fe42206ded3d4cf32b5a31747483c6d85.tar.gz
poky-ef72321fe42206ded3d4cf32b5a31747483c6d85.tar.bz2
poky-ef72321fe42206ded3d4cf32b5a31747483c6d85.zip
bitbake: toaster-tests: maximize browser window when running UI tests
In some pages of the UI, the UI tests failed because parts of the UI which should be visible were being reported as not visible by the Selenium PhantomJS driver. On investigation, it turns out that PhantomJS uses a very narrow default window. This meant that some parts of the UI were being clipped and were thus not "visible" to the driver, causing test failures (specifically, on the new custom image page). Ensure that the window is maximized before running tests to prevent this happening. (Bitbake rev: 3f61bef9359926211be7a3177a2071963726ead5) Signed-off-by: Elliot Smith <elliot.smith@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/toaster/tests')
-rw-r--r--bitbake/lib/toaster/tests/browser/selenium_helpers.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/bitbake/lib/toaster/tests/browser/selenium_helpers.py b/bitbake/lib/toaster/tests/browser/selenium_helpers.py
index 56dbe2b344..54db2e8cf2 100644
--- a/bitbake/lib/toaster/tests/browser/selenium_helpers.py
+++ b/bitbake/lib/toaster/tests/browser/selenium_helpers.py
@@ -130,6 +130,7 @@ class SeleniumTestCase(StaticLiveServerTestCase):
# instantiate the Selenium webdriver once for all the test methods
# in this test case
cls.driver = create_selenium_driver()
+ cls.driver.maximize_window()
@classmethod
def tearDownClass(cls):