qt5base-lts

History

Rohan McGovern 6e50394c4e Reduce usage of Q_ASSERT in autotests. Using Q_ASSERT does nothing in release-mode builds, and in debug builds it causes tests to terminate prematurely. It is much better to use QVERIFY or QCOMPARE. Task-number: QTBUG-17582 Reviewed-by: Rohan McGovern (cherry picked from commit 3475168550c1a804f04f2a4edfeb30c04cd36551) Change-Id: Ic39972b685ca35a9a71d9c8d03e8dae31481fb19		2011-05-18 10:57:56 +10:00
..
arthur	Updated version references in autotests	2011-05-13 15:38:50 +03:00
auto	Reduce usage of Q_ASSERT in autotests.	2011-05-18 10:57:56 +10:00
benchmarks	Updated version references in autotests	2011-05-13 15:38:50 +03:00
global	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	Add missing license headers	2011-05-10 12:54:51 +02:00
shared	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
README	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
tests.pro	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +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.