qt6-bb10

History

Soheil Armin f3f383f097 Android: Add autotest to verify the content of an AAR target This will build a multi-abi Android AAR target and verifies its content using a customer target "verify_aar" by running zipinfo on the AAR, and comparing its content with a subset of files that are expected to be present in the package. Task-number: QTBUG-125483 Change-Id: I19ad132bbad1a75c40b00de173ca09ad56500076 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>		2024-05-27 07:57:47 +00:00
..
auto	Android: Add autotest to verify the content of an AAR target	2024-05-27 07:57:47 +00:00
baseline	Fix test compilation issues with QtLite configuration	2024-05-06 14:29:02 +00:00
benchmarks	Add copyright and licensing to build system files missing it	2024-05-21 17:23:21 +02:00
global	…
libfuzzer	Add CMYK support to QColorSpace	2024-04-12 21:53:54 +02:00
manual	Android: cleanup AndroidManifest.xml files in examples	2024-05-23 17:52:21 +03:00
shared	Replace incorrect Metal config check in nativewindow.h	2024-05-01 14:24:06 +02:00
testserver	Move shbang lines to before copyright headers	2024-05-23 23:58:10 +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.