qt5base-lts

History

Jason McDonald 8094e93e08 Remove Q_ASSERT's from qreadwritelock autotest The tryWriteLock testfunction didn't do anything useful in non-debug builds, due to the thread having the important code inside Q_ASSERT's, which are no-ops in non-debug builds. This commit removes the Q_ASSERT's, counts the number of failures in the thread and fails the test if there are any failures recorded. Change-Id: I4750f66eeba22ab51ba348ebc06704052421f1ae Task-number: QTBUG-17582 Reviewed-by: Rohan McGovern (cherry picked from commit 00f724c943b83f10f9ca9475570708536947538e)		2011-05-18 10:46:47 +10:00
..
arthur	Updated version references in autotests	2011-05-13 15:38:50 +03:00
auto	Remove Q_ASSERT's from qreadwritelock autotest	2011-05-18 10:46:47 +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.