Fix window mapping test by removing peculiar child window test case

Hiding a child window which parent was made invisible before was not
possible in the multi-process scenario. This behavior was fixed in
qtdeclarative 16023fc77c423a267fcc48894ff942e94cf35b86, so the special
test case for this can be dropped. From now on, the behaviors between
single- and multi-process scenarios are the same and the tests also
reflect that.

Change-Id: Icd17e099d21750ab8971ab54dd6efd9ca7894891
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

1 files changed, 1 insertions, 8 deletions

diff --git a/tests/auto/qml/windowmapping/tst_windowmapping.qml b/tests/auto/qml/windowmapping/tst_windowmapping.qml
index 0bcba781..39ea3a5f 100644
--- a/tests/auto/qml/windowmapping/tst_windowmapping.qml
+++ b/tests/auto/qml/windowmapping/tst_windowmapping.qml
@@ -171,15 +171,8 @@ TestCase {
         expectedWindowCount -= 1;
         tryCompare(WindowManager, "count", expectedWindowCount, spyTimeout);
 
-        // Single- vs. multiprocess difference:
         app.start("hide-sub");
-        if (ApplicationManager.singleProcess) {
-            expectedWindowCount -= 1;
-        } else {
-            // This is even more weird Window behavior: when the parent window is invisible, it is
-            // not possible any more to explicitly set the child window to invisible.
-            wait(50 * AmTest.timeoutFactor);
-        }
+        expectedWindowCount -= 1;
         tryCompare(WindowManager, "count", expectedWindowCount, spyTimeout);
     }