qt5base-lts

History

Sona Kurazyan 72e21ad3e9 Add basic benchmarks for QFuture The benchmark simply calls the non-trivial methods of QFuture, mostly to make sure that fixes in the parent patches don't have any performance implications. Task-number: QTBUG-92045 Change-Id: Ib4e8c314a70b3090a1af55f1b96d9dad4bc63861 Reviewed-by: Andrei Golubev <andrei.golubev@qt.io>		2021-06-19 08:48:14 +02:00
..
auto	Move the linking logic of the object libraries to a common function	2021-06-18 23:18:26 +02:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Add basic benchmarks for QFuture	2021-06-19 08:48:14 +02:00
global
libfuzzer	fuzzing: Add instructions how to reproduce issues from oss-fuzz	2021-06-16 22:53:36 +00:00
manual	tests: update startsystemmove manual test with latest api	2021-06-16 15:53:22 +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.