qt5base-lts

History

Thiago Macieira 3a1f4b186d Stop trying to discover the system timer resolution on Windows Let's take the beginning of the description: WaitForSingleObjectEx can be up to 16 milliseconds early. This is proven by the fact that there are tests doing: wait(waitTime); QVERIFY(timer.elapsed() >= waitTime - systemTimersResolution); and failing. Task-number: QTBUG-59337 Change-Id: Iae839f6a131a4f0784bffffd14a9a79523d69d94 Reviewed-by: Olivier Goffart (Woboq GmbH) <ogoffart@woboq.com>		2017-03-08 05:52:47 +00:00
..
auto	Stop trying to discover the system timer resolution on Windows	2017-03-08 05:52:47 +00:00
baselineserver	Properly use the "process" feature	2017-02-27 15:44:46 +00:00
benchmarks	Properly use the "process" feature	2017-02-27 15:44:46 +00:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	use regular configure mechanism for openssl library references	2017-02-22 07:45:59 +00:00
shared	Windows CE cleanup.	2016-04-14 12:45:56 +00:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	Use qtConfig throughout in qtbase	2016-08-19 04:28:05 +00:00

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.