qt5base-lts

History

Thiago Macieira 6ec86513dd Increase the resolution for QDeadlineTimer unit test Apparently, the CI can run something over 1000x slower than on my machine. We're getting over 100 ms delays in operations that shouldn't have taken more than half a millisecond. The last report was of 136% over budget, so I multiplied the resolution by 4. Change-Id: I9093948278414644a416fffd1474406967b2a6ee Reviewed-by: Frederik Gladhorn <frederik.gladhorn@qt.io>		2016-10-26 03:16:26 +00:00
..
auto	Increase the resolution for QDeadlineTimer unit test	2016-10-26 03:16:26 +00:00
baselineserver	Merge remote-tracking branch 'origin/5.7' into dev	2016-05-23 21:09:46 +02:00
benchmarks	Change confusing Q_DEAD_CODE_FROM_QT4_FOO define	2016-10-14 08:19:29 +00:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	port to modularized platformsupport libraries	2016-10-15 18:45:41 +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.