qt5base-lts

History

David Faure d147285d64 Add Q_COREAPP_STARTUP_FUNCTION macro. This is necessary for initializing things in a library, which require a QCoreApplication instance (unlike Q_CONSTRUCTOR_FUNCTION, which runs before that). Example use cases: KCrash (segv handler), and KCheckAccelerators (debugging tool triggered by magic key combination). Change-Id: I5f4c4699dd4d21aea72b007989ba57467e86ed10 Reviewed-by: Olivier Goffart <ogoffart@woboq.com> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2013-01-15 14:58:35 +01:00
..
auto	Add Q_COREAPP_STARTUP_FUNCTION macro.	2013-01-15 14:58:35 +01:00
baselineserver	remove obsolete DEPENDPATH assignments	2012-12-17 14:08:17 +01:00
benchmarks	Benchmarks: Remove declaration of built-in and automatic metatypes.	2013-01-03 18:19:28 +01:00
global	Add bic data for tst_bic	2013-01-06 19:16:02 +01:00
manual	Merge branch 'stable' into dev	2013-01-07 15:18:16 +01:00
shared	Change copyrights from Nokia to Digia	2012-09-22 19:20:11 +02:00
README
tests.pro	Properly implement a 'make docs' target for subdirs and apps/libs	2012-05-09 08:34:42 +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.