qt5base-lts

History

Stephen Kelly 49555e3ac9 Add a CMake macro to test module includes The variations of includes which should work are tested. For example, in the case of testing the QtCore module and QObject include, the following includes are generated and compiled: #include <QObject> #include <QtCore/QObject> #include <QtCore> #include <QtCore/QtCore> As the private include directories are not available to the compiler, this also tests that private headers are not included from public ones. Change-Id: Id03d0fe290c9691e0f7515015892991d1701ab72 Reviewed-by: Stephen Kelly <stephen.kelly@kdab.com>		2012-10-26 15:23:30 +02:00
..
auto	Add a CMake macro to test module includes	2012-10-26 15:23:30 +02:00
baselineserver	Misc. updates to the lancelot autotest framework	2012-09-26 04:03:48 +02:00
benchmarks	normalise signal/slot signatures [QtGui tests]	2012-10-22 08:41:27 +02:00
global
manual	Fix syncing of visibility and enabled for menus on Cocoa	2012-10-26 14:53:09 +02: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.