qt5base-lts

History

Bradley T. Hughes faa6113c41 Fix unstable test due to a race in QThread QThread::finished() is emitted before setting the thread's state to finished and !running, which means it's possible to receive the finished() signal and act on it while QThread::isRunning() still returns true. This test randomly fails due to this race. Fix it by using checking the return value of QThread::wait() instead. Change-Id: Ibf347fc9a2e8d32b328227ee6978e1129dd781f4 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2011-11-03 18:43:52 +01:00
..
auto	Fix unstable test due to a race in QThread	2011-11-03 18:43:52 +01:00
baselineserver	Remove SkipMode parameter from QSKIP calls.	2011-10-21 01:20:29 +02:00
benchmarks	Update QMutex benchmark to match the one in 4.8	2011-10-27 16:32:09 +02:00
global	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	all remaining tests: eliminated usage of qttest_p4.prf	2011-10-25 08:42:23 +02:00
shared	Remove SkipMode parameter from QSKIP calls.	2011-10-21 01:20:29 +02:00
README
tests.pro	disable autotests temporarily on Mac	2011-09-14 13:55:41 +02:00

README

This directory contains autotests and benchmarks based on QTestlib. 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.