qt5base-lts

History

Svenn-Arne Dragly ce08318a46 Add QThreadPool autotest to detect stale threads after tryTake This test makes sure that we do not introduce a regression where the threads exited the inner loop over the queue before the queue was empty. This was triggered by calling tryTake at least maxThreadCount times, which left the same number of null pointers in the queue and caused the inner loop to exit too soon for all the threads. Change-Id: I3a9d800149b88d09510ddc424667670b60f06a33 Reviewed-by: Lars Knoll <lars.knoll@qt.io>		2017-11-16 12:42:44 +00:00
..
auto	Add QThreadPool autotest to detect stale threads after tryTake	2017-11-16 12:42:44 +00:00
baselineserver	tests: Add Q_FALLTHROUGH to unmarked fallthroughs seen by GCC 7	2017-06-28 17:57:35 +00:00
benchmarks	Restore compatibility with pre-5.9 Keccak calculation	2017-09-21 03:21:58 +00:00
global
manual	QCocoaMenu: Attach menu items when updating the menubar	2017-11-05 01:39:30 +00:00
shared	Fix largefile tests on ARM and QEMU targets	2017-03-28 06:55:32 +00:00
README
tests.pro	Build examples and tests only if their requirements are met	2017-03-22 15:55:55 +00:00

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.