qt5base-lts

History

Stephen Kelly c18a41197f Find Qt5 modules automatically in the qt5_use_modules function. This ensures that we only find Qt5 modules from the same directory as modules we have already found, not from multiple different directories which may be incompatible. Change-Id: I7ad1d81ec41bba2e543130740041338ba44a6c3b Reviewed-by: Alexander Neundorf <neundorf@kde.org> Reviewed-by: Stephen Kelly <stephen.kelly@kdab.com>		2012-05-14 04:35:01 +02:00
..
auto	Find Qt5 modules automatically in the qt5_use_modules function.	2012-05-14 04:35:01 +02:00
baselineserver	baselineserver: Fix compilation by removing PI_BuildKey from the source	2012-04-25 19:52:22 +02:00
benchmarks	Change remaining uses of {to,from}Ascii to {to,from}Latin1 [QtDBus]	2012-05-07 05:05:30 +02:00
global	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	Enable specifying raw headers for the request	2012-05-05 03:50:41 +02:00
shared	Fix MSVC warnings in tests.	2012-04-02 16:56:48 +02:00
README	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
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.