qt5base-lts

History

Jason McDonald e822eb1a65 Use standard method of excluding a test. If we find out at run-time that an entire test program is not applicable, the correct way to skip the test is by calling QSKIP from the test's initTestCase() method. Change-Id: Iaf1dbcce38c569ee9513bf37232e9e4ea287d872 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>		2011-10-27 11:14:44 +02:00
..
auto	Use standard method of excluding a test.	2011-10-27 11:14:44 +02:00
baselineserver	Remove SkipMode parameter from QSKIP calls.	2011-10-21 01:20:29 +02:00
benchmarks	benchmarks: eliminated usage of qttest_p4.prf	2011-10-25 08:42:23 +02:00
global	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	all remaining tests: eliminated usage of qttest_p4.prf	2011-10-25 08:42:23 +02:00
shared	Remove SkipMode parameter from QSKIP calls.	2011-10-21 01:20:29 +02:00
README	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
tests.pro	disable autotests temporarily on Mac	2011-09-14 13:55:41 +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.