qt5base-lts

History

Simo Fält c1f76a3347 Adding CI utilities to Android test script It is now configurable if test results are stored in xml, plain text or in both formats. Default is xml, like it was, Max runtime is also configurable so that we can reduce the CI round. With default setting it takes more than eight hours within current CI node. The latest test result dir is linked as latest. Change-Id: I5d27cefe17e4f86648132db7ec104711d993c3de Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>		2013-10-30 11:29:04 +01:00
..
auto	Adding CI utilities to Android test script	2013-10-30 11:29:04 +01:00
baselineserver	Add QT_NO_PROCESS guards in tests where they are missing	2013-09-03 08:42:24 +02:00
benchmarks	Allow non-character codes in utf8 strings	2013-10-17 09:50:58 +02:00
global
manual	Add widget replace function to QLayout	2013-09-21 23:17:55 +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

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.