qt5base-lts

History

Sergio Ahumada 704a4e4747 test: Don't fail if the network test server is not set up Not having access to a network test server is not a failure per se but rather an enviromental condition not met at run-time. Change-Id: Ie7d10ca5fbf2df45fb1fd1ac19718c9fae855c03 Reviewed-by: Caroline Chao <caroline.chao@digia.com>		2012-10-25 14:10:04 +02:00
..
auto	test: Don't fail if the network test server is not set up	2012-10-25 14:10:04 +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	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	normalise signal/slot signatures [QtNetwork tests]	2012-10-19 00:44:54 +02:00
shared	Change copyrights from Nokia to Digia	2012-09-22 19:20:11 +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.