qt6-bb10

History

Axel Spoerl bf44ca3224 Add QProgressBar test in tst_baseline_widgets Task-number: QTBUG-99678 Pick-to: 6.3 Change-Id: Ib56f7bdcc1e61d0354a7a381b8089f35e80b931c Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>		2022-01-14 13:33:24 +01:00
..
auto	Improve QShortcut test	2022-01-13 21:00:22 +00:00
baseline	Add QProgressBar test in tst_baseline_widgets	2022-01-14 13:33:24 +01:00
benchmarks	Fix the benchmark for QList::removeAll()	2021-12-09 03:45:08 +01:00
global	…
libfuzzer	Fuzzing: Don't explicitly restrict sizes before loading images	2022-01-12 22:10:01 +00:00
manual	rhi: Add the basic infrastructure for tessellation support	2022-01-13 13:44:29 +01:00
shared	QtBase: replace windows.h with qt_windows.h	2021-11-23 12:53:46 +08: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.