qt5base-lts

History

Shawn Rutledge 1500d2283e Clear only one device from g_pointIdMap when all points released The new test tst_QTouchEvent::touchOnMultipleTouchscreens() needs the touchpoint IDs to be predictable, but another test currently has a QEXPECT_FAIL; without release events, g_pointIdMap continued to hold the touchpoints that were there when the test failed. So it's necessary to add QWindowSystemInterfacePrivate::clearPointIdMap() to be able to call it in the test cleanup function. Fixes: QTBUG-73830 Change-Id: Ia6a70d028be95cd2b6676db6363ec408c0b116bc Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>		2019-02-26 19:52:25 +00:00
..
auto	Clear only one device from g_pointIdMap when all points released	2019-02-26 19:52:25 +00:00
baselineserver	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
benchmarks	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
global
manual	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
shared	tests: Include QFileInfo in emulationdetector.h	2018-05-14 12:36:28 +00:00
testserver	Rework QNetworkReply tests to use docker-based test servers	2018-07-27 17:40:27 +00:00
README
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.