qt5base-lts

History

David Faure 78b8f7803b QtConcurrentRun: add unittest for polling for isFinished() I had intermittent failures with this kind of code in my unittests, not sure why yet. This test seems to pass reliably, apart from helgrind saying it triggers the known race in QFuture::isFinished, for which Marc is working on a fix. Change-Id: I4aabe77566dc1af859a016ffe8a4cce19ddf25c8 Reviewed-by: Marc Mutz <marc.mutz@kdab.com>		2016-02-15 13:53:57 +00:00
..
auto	QtConcurrentRun: add unittest for polling for isFinished()	2016-02-15 13:53:57 +00:00
baselineserver	Updated license headers	2016-01-21 18:55:18 +00:00
benchmarks	Add Intel copyright to files that Intel has had non-trivial contribution	2016-01-21 22:44:21 +00:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	Merge remote-tracking branch 'origin/5.6' into dev	2016-02-02 15:57:44 +01:00
shared	Updated license headers	2016-01-21 18:55:18 +00:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	iOS: Enable building of basic tests	2014-01-22 12:35:17 +01: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.