qt5base-lts

History

Friedemann Kleint 6bb22c12a6 rcc test: Properly check QProcess errors Separate waitForStarted() and waitForFinished() to properly catch startup errors and kill hanging processes. Also check exit status and code. Task-number: PYSIDE-855 Change-Id: Ic8e623f4a8c716a2892767a8dbc06ba4ffb90b5a Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>		2019-03-05 18:28:15 +00:00
..
auto	rcc test: Properly check QProcess errors	2019-03-05 18:28:15 +00:00
baselineserver	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
benchmarks	Merge remote-tracking branch 'origin/5.12' into 5.13	2019-02-19 01:00:08 +01:00
global
libfuzzer	Add libfuzzer test for QTextDocument::setHtml()	2019-01-24 18:21:19 +00:00
manual	Merge remote-tracking branch 'origin/5.12' into 5.13	2019-02-19 01:00:08 +01:00
shared	tst_qfileinfo: Refactor ntfsJunctionPointsAndSymlinks()	2018-09-30 09:59:09 +00:00
testserver	Port tst_qtcpsocket to the docker server	2019-02-28 15:48:31 +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.