From bae03680347280ca8c1810fc8c92503f6f346068 Mon Sep 17 00:00:00 2001 From: Christian Stenger Date: Wed, 10 May 2017 14:52:51 +0200 Subject: [PATCH] Squish: Fix switching to build or run settings If too many kits are present and/or the screen resolution is too low to have QC having the correct minimum windows size Squish fails to click on the items as it might be necessary to scroll to them to have them really (user-) visible. There is an obvious difference between 'visible' for Squish and 'visible' for the interacting user. Change-Id: Id658a323fcf2ae3882b225c6ce9383ed2c876e81 Reviewed-by: Robert Loehning --- tests/system/shared/project_explorer.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/system/shared/project_explorer.py b/tests/system/shared/project_explorer.py index 2396bbc80f1..686d5722e25 100644 --- a/tests/system/shared/project_explorer.py +++ b/tests/system/shared/project_explorer.py @@ -100,7 +100,9 @@ def switchToBuildOrRunSettingsFor(targetCount, currentTarget, projectSettings): if not test.verify(not str(findObject(currentTargetIndex).toolTip).startswith(clickToActivate), "Verifying target '%s' is enabled." % targets[currentTarget]): return False - mouseClick(waitForObject(currentTargetIndex)) + index = waitForObject(currentTargetIndex) + treeView.scrollTo(index) + mouseClick(index) if projectSettings == ProjectSettings.BUILD: settingsIndex = getQModelIndexStr("text='Build'", currentTargetIndex)