qt5base-lts

History

Thiago Macieira 73251f22f3 Add a Qt-API style QStandardPaths::setTestModeEnabled QStandardPaths::enableTestMode has a verb in the imperative ("enable") as the core word in the name. That indicates an action. The function should not have had a parameter. Instead, add a Qt-style setXXXEnabled function. [ChangeLog][QtCore][QStandardPaths] QStandardPaths::enableTestMode is deprecated and is replaced by QStandardPaths::setTestModeEnabled. Change-Id: Ib26ad72d7c635890d2cb22ae9d44cbda08a6f17c Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com> Reviewed-by: David Faure (KDE) <faure@kde.org>		2013-08-09 21:25:24 +02:00
..
auto	Add a Qt-API style QStandardPaths::setTestModeEnabled	2013-08-09 21:25:24 +02:00
baselineserver	Whitespace cleanup: remove trailing whitespace	2013-03-16 20:22:50 +01:00
benchmarks	Fix compilation of the tst_qnetworkreply benchmark test with QT_NO_SSL.	2013-07-19 14:16:42 +02:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	QTreeView - allow users to control data in the treestructure	2013-08-07 14:01:23 +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.