qt5base-lts

History

David Faure b61cff8d6e qprocess autotests don't need QtGui (this isn't true of -all- corelib/ autotests though, e.g. tst_qdatastream uses QBitmap) Change-Id: I314fda5d85d45cb5eece8da74156989b83cf0299 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2013-02-09 18:44:41 +01:00
..
auto	qprocess autotests don't need QtGui	2013-02-09 18:44:41 +01:00
baselineserver	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01:00
benchmarks	Remove QT_{BEGIN,END}_HEADER macro usage	2013-01-29 01:06:04 +01:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	QColorDialog manual test: add initial color selection	2013-02-07 01:22:40 +01:00
shared	Update copyright year in Digia's license headers	2013-01-18 09:07:35 +01: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.