qt6-bb10

History

Simon Hausmann dcecaeb7b9 Prospective fix to stabilize tst_qwindow::isActive() on Windows 10 It is conceivable that during the try-compare loop of processing windowing system events we loose and regain the focus. That would explain the occasional test failure where instead of the expected 3 focus in events, we have received four. Task-number: QTBUG-77769 Change-Id: I2221440d09a74d4d18a72f7786232b4491cf45a8 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> (cherry picked from commit `56f084781e`) Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>		2019-10-03 15:09:16 +00:00
..
auto	Prospective fix to stabilize tst_qwindow::isActive() on Windows 10	2019-10-03 15:09:16 +00:00
baselineserver	Merge remote-tracking branch 'origin/5.13' into 5.14	2019-09-09 07:51:49 +00:00
benchmarks	QReadWriteLock: add a check for writeOnly, too	2019-09-12 06:38:42 +02:00
global	…
libfuzzer	Harden ICC parser	2019-07-31 21:47:04 +02:00
manual	rhi: Remove QVectors from the data description structs as well	2019-10-03 09:37:48 +02:00
shared	Remove usages of Q_OS_WINCE	2019-05-23 13:51:05 +02:00
testserver	Share the common configurations among different modules	2019-07-01 01:09:42 +02:00
README	…
tests.pro	…

README

This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.

Linux X11:

   * The user must be logged in to an active desktop; you can't run the
     autotests without a valid DISPLAY that allows X11 connections.

   * The tests are run against a KDE3 or KDE4 desktop.

   * Window manager uses "click to focus", and not "focus follows mouse". Many
     tests move the mouse cursor around and expect this to not affect focus
     and activation.

   * Disable "click to activate", i.e., when a window is opened, the window
     manager should automatically activate it (give it input focus) and not
     wait for the user to click the window.