qt5base-lts

History

Marc Mutz 542ba86e22 tests/auto/corelib/mimetypes: use local QThreadPool Isolates the test from anything that might be going on on the globalInstance(). Enabled by the explicit thread-pool feature on QtConcurrent::run(). Add explicit timed wait (unit tests should contain as little indefinite waits as possible). Also avoids the use of QFutureSynchronizer, which makes my static QList checker go nuts, with no way of fixing it until Qt 6. Change-Id: I0829992642b2a49bb6a10ddd4b31eb3f88e3adeb Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2016-09-17 06:47:05 +00:00
..
auto	tests/auto/corelib/mimetypes: use local QThreadPool	2016-09-17 06:47:05 +00:00
baselineserver	Merge remote-tracking branch 'origin/5.7' into dev	2016-05-23 21:09:46 +02:00
benchmarks	Modularize configure.json/.pri	2016-09-15 08:23:53 +00:00
global
manual	Merge remote-tracking branch 'origin/5.7' into 5.8	2016-08-29 15:30:17 +02:00
shared	Windows CE cleanup.	2016-04-14 12:45:56 +00:00
README
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.