qt5base-lts

History

Andrew Knight cd582f8410 Add QT_NO_PROCESS guards in tests where they are missing A handful of tests lack QT_NO_PROCESS guards, making them non-compilable on Qt builds with no QProcess support. This commit does not change QProcess-specific tests, which should be left out of the build using the .pro file mechanism. Change-Id: Iac8562428abc1f59ccbb23bf5c3a919785e41f12 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>		2013-09-03 08:42:24 +02:00
..
auto	Add QT_NO_PROCESS guards in tests where they are missing	2013-09-03 08:42:24 +02:00
baselineserver	Add QT_NO_PROCESS guards in tests where they are missing	2013-09-03 08:42:24 +02:00
benchmarks	Add benchmark for QThreadPool.	2013-08-21 23:50:23 +02:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	QTreeView - fix next focus when there is no current index	2013-08-30 21:07:46 +02:00
shared	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01: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 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.