qt6-bb10

History

Alexey Edelev d02c3151b2 Disable android_deployment_settings test for non-standalone scenario The test changes couple variables to emulate the user project environment. These variables also affect the policy handling. The test will build and work properly only if tests are built standalone. So add this limitation. Amends `2e340cea88` Pick-to: 6.6 Change-Id: I0cc49bf55bf7763e4c3ecdfa5333fb0453f06794 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2023-08-25 18:37:23 +02:00
..
auto	Disable android_deployment_settings test for non-standalone scenario	2023-08-25 18:37:23 +02:00
baseline	Mark all of Qt as free of Q_FOREACH, except where it isn't	2023-08-19 05:19:42 +00:00
benchmarks	Mark all of Qt as free of Q_FOREACH, except where it isn't	2023-08-19 05:19:42 +00:00
global	…
libfuzzer	Change the license of all CMakeLists.txt and *.cmake files to BSD	2022-08-23 23:58:42 +02:00
manual	Mark all of Qt as free of Q_FOREACH, except where it isn't	2023-08-19 05:19:42 +00:00
shared	Add embeddedwindows manual test	2023-08-07 22:59:19 +02:00
testserver	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
CMakeLists.txt	Rid of 'special case' markers	2023-04-13 18:30:58 +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.