qt5base-lts

History

Edward Welbourne 4ccbd751f1 Use a scope-guard to take care of process deletion in a test Doing the deletion at the end of the block only works if the test passes. Drive-by: remove spurious braces from single-line bodies of single-line controls. The QTest macros are done properly. Pick-to: 6.2 6.1 5.15 Change-Id: I83002547dba49ab9792f4db44d73151b1c036900 Reviewed-by: Sona Kurazyan <sona.kurazyan@qt.io>		2021-08-17 19:18:54 +02:00
..
auto	Use a scope-guard to take care of process deletion in a test	2021-08-17 19:18:54 +02:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Add benchmark for QMetaEnum	2021-08-16 19:26:29 +02:00
global
libfuzzer	Remove dysfunctional -coverage configure argument	2021-08-10 12:00:13 +02:00
manual	QNetworkInformation: Give the manual test a GUI	2021-07-13 16:37:19 +02:00
shared	Refactor createSymbolicLink() and createNtfsJunction()	2021-06-02 23:02:45 +02:00
testserver	Network self-test: make it work with docker/containers	2020-11-17 19:56:06 +01:00
CMakeLists.txt	CMake: Refactor optimization flag handling and add optimize_full	2020-10-06 10:07:05 +02:00
README

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.